All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Alice Ryhl <aliceryhl@google.com>
Subject: Re: [GIT PULL v2] tracing: Updates for v6.14
Date: Tue, 21 Jan 2025 11:41:00 -0500	[thread overview]
Message-ID: <Z4_OHKESRSiJcr-b@lappy> (raw)
In-Reply-To: <20250121101551.2ad87b73@gandalf.local.home>

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.

-- 
Thanks,
Sasha

  reply	other threads:[~2025-01-21 16:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-21 15:15 [GIT PULL v2] tracing: Updates for v6.14 Steven Rostedt
2025-01-21 16:41 ` Sasha Levin [this message]
2025-01-21 17:41   ` Steven Rostedt
2025-01-21 18:02     ` Sasha Levin
2025-01-21 18:39       ` Steven Rostedt
2025-01-21 19:09         ` Sasha Levin
2025-01-21 19:11           ` Steven Rostedt
2025-01-21 19:39             ` Steven Rostedt
2025-01-24  2:07 ` pr-tracker-bot

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=Z4_OHKESRSiJcr-b@lappy \
    --to=sashal@kernel.org \
    --cc=aliceryhl@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.