Regression on linux-next (next-20250120)
Borah, Chaitanya Kumar
chaitanya.kumar.borah at intel.com
Fri Jan 24 13:55:07 UTC 2025
> -----Original Message-----
> From: Al Viro <viro at ftp.linux.org.uk> On Behalf Of Al Viro
> Sent: Thursday, January 23, 2025 11:49 PM
> To: Borah, Chaitanya Kumar <chaitanya.kumar.borah at intel.com>
> Cc: intel-gfx at lists.freedesktop.org; intel-xe at lists.freedesktop.org; Kurmi,
> Suresh Kumar <suresh.kumar.kurmi at intel.com>; Saarinen, Jani
> <jani.saarinen at intel.com>; linux-fsdevel at vger.kernel.org
> Subject: Re: Regression on linux-next (next-20250120)
>
> On Thu, Jan 23, 2025 at 03:41:08PM +0000, Borah, Chaitanya Kumar wrote:
> > Hello Al,
> >
> > Hope you are doing well. I am Chaitanya from the linux graphics team in
> Intel.
> >
> > This mail is regarding a regression we are seeing in our CI runs[1] on linux-
> next repository.
> >
> > Since the version next-20250120 [2], we are seeing the following
> > regression
>
> Ugh... To narrow the things down, could you see if replacing
> fsd = kmalloc(sizeof(*fsd), GFP_KERNEL); with
> fsd = kzalloc(sizeof(*fsd), GFP_KERNEL); in
> fs/debugfs/file.c:__debugfs_file_get() affects the test?
This change seems to help. Can we expect a fix patch?
Thank you.
Regards
Chaitanya
More information about the Intel-xe
mailing list