On Tue, Feb 11, 2025 at 12:30:01PM +0000, Borah, Chaitanya Kumar wrote: > Hello Mike, > > > -----Original Message----- > > From: Mike Rapoport <rppt@xxxxxxxxxx> > > Sent: Tuesday, February 11, 2025 1:21 PM > > To: Borah, Chaitanya Kumar <chaitanya.kumar.borah@xxxxxxxxx> > > Cc: intel-gfx@xxxxxxxxxxxxxxxxxxxxx; intel-xe@xxxxxxxxxxxxxxxxxxxxx; Saarinen, > > Jani <jani.saarinen@xxxxxxxxx>; Kurmi, Suresh Kumar > > <suresh.kumar.kurmi@xxxxxxxxx>; x86@xxxxxxxxxx; De Marchi, Lucas > > <lucas.demarchi@xxxxxxxxx> > > Subject: Re: Regression on linux-next (next-20250205) > > > > Hello Chaitanya, > > > > On Mon, Feb 10, 2025 at 06:52:35AM +0000, Borah, Chaitanya Kumar > > wrote: > > > Hello Mike, > > > > > > 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-20250205 [2], we are seeing the following > > > regression > > > > > > `````````````````````````````````````````````````````````````````````` > > > ``````````` <4>[ 314.781734] kmemleak: Found object by alias at > > > 0xffffffffa0595000 <4>[ 314.781738] CPU: 11 UID: 0 PID: 6042 Comm: > > > i915_selftest Tainted: G U > > > 6.14.0-rc1-next-20250205-next-20250205-ged88b8b82c53+ #1 <4>[ > > > 314.781741] Tainted: [U]=USER <4>[ 314.781741] Hardware name: ASUS > > > System Product Name/PRIME Z790-P WIFI, BIOS 0812 02/24/2023 > > <4>[ 314.781742] Call Trace: > > > <4>[ 314.781743] <TASK> > > > <4>[ 314.781744] dump_stack_lvl+0x91/0xf0 <4>[ 314.781749] > > > dump_stack+0x10/0x20 <4>[ 314.781751] __lookup_object+0x90/0xa0 > > <4>[ > > > 314.781755] __find_and_get_object+0x6c/0x190 <4>[ 314.781758] > > > paint_ptr+0x1b/0xa0 <4>[ 314.781759] kmemleak_not_leak+0x33/0x70 > > > <4>[ 314.781762] load_module+0xa20/0x2d10 > > > `````````````````````````````````````````````````````````````````````` > > > ``````````` > > > Details log can be found in [3]. > > > > Does this fix it for you? > > > > > > diff --git a/kernel/module/main.c b/kernel/module/main.c index > > 4a02503836d7..a598888e7072 100644 > > --- a/kernel/module/main.c > > +++ b/kernel/module/main.c > > @@ -1260,7 +1260,8 @@ static int module_memory_alloc(struct module > > *mod, enum mod_mem_type type) > > * *do* eventually get freed, but let's just keep things simple > > * and avoid *any* false positives. > > */ > > - kmemleak_not_leak(ptr); > > + if (!mod->mem[type].is_rox) > > + kmemleak_not_leak(ptr); > > > > memset(ptr, 0, size); > > mod->mem[type].base = ptr; > > > > > > Thank you for your reply. > > Unfortunately, the change makes it worse. Our local system seems to be in continuous reboot. Are there any logs available? > Regards > > Chaitanya > > > > [1] https://intel-gfx-ci.01.org/tree/linux-next/combined-alt.html? > > > [2] > > > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/co > > > mmit/?h=next-20250205 [3] > > > https://intel-gfx-ci.01.org/tree/linux-next/next-20250205/bat-rpls-4/d > > > mesg0.txt [4] > > > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/co > > > mmit/?h=next- > > 20250205&id=64f6a4e10c05ed527f0f24b7954964255e0d3535 > > > > > > Regards > > > Chaitanya > > > > -- > > Sincerely yours, > > Mike. -- Sincerely yours, Mike.
