Regression on linux-next (next-20250205)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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].

After bisecting the tree, the following patch [4] seems to be the first "bad"
commit

`````````````````````````````````````````````````````````````````````````````````````````````````````````
commit 64f6a4e10c05ed527f0f24b7954964255e0d3535
Author: Mike Rapoport (Microsoft) mailto:rppt@xxxxxxxxxx
Date:   Sun Jan 26 09:47:33 2025 +0200

    x86: re-enable EXECMEM_ROX support

    after rework of execmem ROX caches

    Signed-off-by: "Mike Rapoport (Microsoft)" mailto:rppt@xxxxxxxxxx
    Signed-off-by: Peter Zijlstra (Intel) mailto:peterz@xxxxxxxxxxxxx
    Link: https://lore.kernel.org/r/20250126074733.1384926-10-rppt@xxxxxxxxxx

`````````````````````````````````````````````````````````````````````````````````````````````````````````

We also verified that if we revert the patch the issue is not seen.

Could you please check why the patch causes this regression and provide a fix if necessary?

Thank you.

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/commit/?h=next-20250205
[3] https://intel-gfx-ci.01.org/tree/linux-next/next-20250205/bat-rpls-4/dmesg0.txt
[4] https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20250205&id=64f6a4e10c05ed527f0f24b7954964255e0d3535

Regards

Chaitanya





[Index of Archives]     [AMD Graphics]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux