From: Kyle Zeng <zengyhkyle@gmail.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org
Subject: Re: wild pointer access in rsvp classifer in the Linux kernel <= v6.2
Date: Wed, 13 Sep 2023 17:04:16 -0700 [thread overview]
Message-ID: <ZQJOAAu0QvKGjDXC@westworld> (raw)
In-Reply-To: <2023091320-chemist-dragonish-6874@gregkh>
On Wed, Sep 13, 2023 at 10:12:55AM +0200, Greg KH wrote:
> On Mon, Sep 11, 2023 at 07:51:38PM -0700, Kyle Zeng wrote:
> > On Fri, Sep 08, 2023 at 07:17:12AM +0100, Greg KH wrote:
> > > Great, can you use 'git bisect' to track down the commit that fiexes
> > > this so we can add it to the stable trees?
> > Sorry for the late reply. I think the fix was to completely retire the
> > rsvp classifier and the commit is:
> >
> > 265b4da82dbf5df04bee5a5d46b7474b1aaf326a (net/sched: Retire rsvp classifier)
>
> Great, so if we apply this change, all will work properly again? How
> far back should this be backported to?
>
> thanks,
>
> greg k-h
> Great, so if we apply this change, all will work properly again?
Yes, after applying the patch (which is to retire the rsvp classifier),
it is no longer possible to trigger the crash.
However, you might want to decide whether it is OK to retire the
classifier in stable releases.
> How far back should this be backported to?
I tested all the stable releases today, namely, v6.1.y, v5.15.y,
v5.10.y, v5.4.y, v4.19.y, and v4.14.y. They are all affected by this
bug. I think the best approach is to apply the patch to all the stable
trees.
Thanks,
Kyle Zeng
next prev parent reply other threads:[~2023-09-14 0:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-08 0:01 wild pointer access in rsvp classifer in the Linux kernel <= v6.2 Kyle Zeng
2023-09-08 6:17 ` Greg KH
2023-09-12 2:51 ` Kyle Zeng
2023-09-13 8:12 ` Greg KH
2023-09-14 0:04 ` Kyle Zeng [this message]
2023-09-16 11:41 ` Greg KH
2023-09-20 2:27 ` Kyle Zeng
2023-09-20 11:10 ` Greg KH
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=ZQJOAAu0QvKGjDXC@westworld \
--to=zengyhkyle@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=stable@vger.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