From: Mike Rapoport <rppt@kernel.org>
To: "Borah, Chaitanya Kumar" <chaitanya.kumar.borah@intel.com>
Cc: "intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"Saarinen, Jani" <jani.saarinen@intel.com>,
"Kurmi, Suresh Kumar" <suresh.kumar.kurmi@intel.com>,
"x86@kernel.org" <x86@kernel.org>,
"De Marchi, Lucas" <lucas.demarchi@intel.com>
Subject: Re: Regression on linux-next (next-20250205)
Date: Tue, 11 Feb 2025 09:50:55 +0200 [thread overview]
Message-ID: <Z6sBX-tPotgS2ARh@kernel.org> (raw)
In-Reply-To: <SJ1PR11MB6129A45FFE75371036820909B9F22@SJ1PR11MB6129.namprd11.prod.outlook.com>
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;
> [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
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2025-02-11 7:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-10 6:52 Regression on linux-next (next-20250205) Borah, Chaitanya Kumar
2025-02-11 7:50 ` Mike Rapoport [this message]
2025-02-11 12:30 ` Borah, Chaitanya Kumar
2025-02-12 6:45 ` Mike Rapoport
2025-02-13 17:30 ` Borah, Chaitanya Kumar
2025-02-14 9:08 ` Mike Rapoport
2025-02-11 8:44 ` ✗ Fi.CI.BUILD: failure for " Patchwork
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Z6sBX-tPotgS2ARh@kernel.org \
--to=rppt@kernel.org \
--cc=chaitanya.kumar.borah@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.saarinen@intel.com \
--cc=lucas.demarchi@intel.com \
--cc=suresh.kumar.kurmi@intel.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox