From: "Jiayuan Chen" <jiayuan.chen@linux.dev>
To: "Steven Rostedt" <rostedt@goodmis.org>,
"Eric Dumazet" <edumazet@google.com>
Cc: netdev@vger.kernel.org,
syzbot+9b35e9bc0951140d13e6@syzkaller.appspotmail.com,
"David S. Miller" <davem@davemloft.net>,
"David Ahern" <dsahern@kernel.org>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
"Simon Horman" <horms@kernel.org>,
"Sebastian Andrzej Siewior" <bigeasy@linutronix.de>,
"Clark Williams" <clrkwllms@kernel.org>,
linux-kernel@vger.kernel.org, linux-rt-devel@lists.linux.dev
Subject: Re: [PATCH net v2] ipv6: fix a BUG in rt6_get_pcpu_route() under PREEMPT_RT
Date: Tue, 23 Dec 2025 02:38:05 +0000 [thread overview]
Message-ID: <7f7c32e627e7d0fd1be12865f253a67cd3af29a8@linux.dev> (raw)
In-Reply-To: <20251222122628.38e9bc89@gandalf.local.home>
December 23, 2025 at 01:26, "Steven Rostedt" <rostedt@goodmis.org mailto:rostedt@goodmis.org?to=%22Steven%20Rostedt%22%20%3Crostedt%40goodmis.org%3E > wrote:
>
> On Mon, 22 Dec 2025 12:16:39 -0500
> Steven Rostedt <rostedt@goodmis.org> wrote:
>
> >
> > On Mon, 22 Dec 2025 09:50:58 +0100
> > Eric Dumazet <edumazet@google.com> wrote:
> >
> > > Link: https://syzkaller.appspot.com/bug?extid=9b35e9bc0951140d13e6
> > > Fixes: 951f788a80ff ("ipv6: fix a BUG in rt6_get_pcpu_route()")
> >
> > I would rather find when PREEMPT_RT was added/enabled, there is no
> > point blaming such an old commit
> > which was correct at the time, and forcing pointless backports to old
> > linux kernels.
> >
> > Ack!
> >
> Fixes: d2d6422f8bd1 ("x86: Allow to enable PREEMPT_RT.")
>
> That was the first commit to enable PREEMPT_RT on any architecture (just
> happened to be x86).
>
> -- Steve
>
Thanks Steve, it helped a lot !
prev parent reply other threads:[~2025-12-23 2:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-19 2:51 [PATCH net v2] ipv6: fix a BUG in rt6_get_pcpu_route() under PREEMPT_RT Jiayuan Chen
2025-12-22 8:50 ` Eric Dumazet
2025-12-22 17:16 ` Steven Rostedt
2025-12-22 17:26 ` Steven Rostedt
2025-12-23 2:38 ` Jiayuan Chen [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=7f7c32e627e7d0fd1be12865f253a67cd3af29a8@linux.dev \
--to=jiayuan.chen@linux.dev \
--cc=bigeasy@linutronix.de \
--cc=clrkwllms@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rostedt@goodmis.org \
--cc=syzbot+9b35e9bc0951140d13e6@syzkaller.appspotmail.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 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.