From: Steven Rostedt <rostedt@goodmis.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Saravana Kannan <saravanak@google.com>,
luogengkun@huaweicloud.com, mathieu.desnoyers@efficios.com,
mhiramat@kernel.org, runpinglai@google.com,
torvalds@linux-foundation.org, wattson-external@google.com,
stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] tracing: Have trace_marker use per-cpu data to read user" failed to apply to 6.12-stable tree
Date: Tue, 14 Oct 2025 08:34:52 -0400 [thread overview]
Message-ID: <20251014083452.10235c41@gandalf.local.home> (raw)
In-Reply-To: <2025101418-buckle-morally-2eb9@gregkh>
On Tue, 14 Oct 2025 07:10:48 +0200
Greg KH <gregkh@linuxfoundation.org> wrote:
> >
> > IIRC, this is a fix for something that went in after 6.12. So, don't
> > need to backport it 6.12 or older.
>
> The "Fixes:" tag references a commit that is in the following releases
> already:
> 5.10.245 5.15.194 6.1.153 6.6.107 6.12.48 6.16.8 6.17
> so that's what triggered this message.
>
Correct. The bug has been there "forever", but because it required
PREEMPT_NONE to trigger, and most people don't use that, it hasn't been
reported.
The fix to the PREEMPT_NONE issue had a regression, thus both fixes
technically need to go back to the beginning.
If I get time, I could work on backporting these patches.
-- Steve
prev parent reply other threads:[~2025-10-14 12:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-13 8:26 FAILED: patch "[PATCH] tracing: Have trace_marker use per-cpu data to read user" failed to apply to 6.12-stable tree gregkh
2025-10-13 19:42 ` Saravana Kannan
2025-10-14 5:10 ` Greg KH
2025-10-14 12:34 ` Steven Rostedt [this message]
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=20251014083452.10235c41@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=gregkh@linuxfoundation.org \
--cc=luogengkun@huaweicloud.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=runpinglai@google.com \
--cc=saravanak@google.com \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=wattson-external@google.com \
/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