[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Z4_hNvl2wLWFC1Va@lappy>
Date: Tue, 21 Jan 2025 13:02:30 -0500
From: Sasha Levin <sashal@...nel.org>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
LKML <linux-kernel@...r.kernel.org>,
Masami Hiramatsu <mhiramat@...nel.org>,
Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
Alice Ryhl <aliceryhl@...gle.com>
Subject: Re: [GIT PULL v2] tracing: Updates for v6.14
On Tue, Jan 21, 2025 at 12:41:02PM -0500, Steven Rostedt wrote:
>On Tue, 21 Jan 2025 11:41:00 -0500
>Sasha Levin <sashal@...nel.org> wrote:
>
>> Hey Steve,
>>
>> I've started seeing memory corruption issues in LKFT, such as the one
>> here: https://qa-reports.linaro.org/lkft/sashal-linus-next/build/v6.13-rc7-790-gabac258eb0d1/testrun/26834686/suite/log-parser-test/test/bug-bug-kernel-null-pointer-dereference-address/log
>>
>> I ran a bisection, which led me to the below commit:
>>
>> On Tue, Jan 21, 2025 at 10:15:51AM -0500, Steven Rostedt wrote:
>> > tracing: Cache ":mod:" events for modules not loaded yet
>>
>> I've also confirmed that reverting this commit on top of linus-next fixes
>> the issue.
>
>Do you have the .config for this? Did you have CONFIG_MODULES set? If not, the bug with:
I've attached it.
> #if CONFIG_MODULES
>
>still is true and the code paths there can cause memory corruption. Which
>would be fixed by the new patches added in this version of the pull request.
CONFIG_MODULES is set (and the log indicates we have loaded a single
module).
--
Thanks,
Sasha
View attachment "config" of type "text/plain" (154100 bytes)
Powered by blists - more mailing lists