From: Greg KH <gregkh@linuxfoundation.org>
To: Kyle Zeng <zengyhkyle@gmail.com>
Cc: stable@vger.kernel.org
Subject: Re: wild pointer access in rsvp classifer in the Linux kernel <= v6.2
Date: Wed, 13 Sep 2023 10:12:55 +0200 [thread overview]
Message-ID: <2023091320-chemist-dragonish-6874@gregkh> (raw)
In-Reply-To: <ZP/SOqa0M3RvrVEF@westworld>
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
next prev parent reply other threads:[~2023-09-13 8:12 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 [this message]
2023-09-14 0:04 ` Kyle Zeng
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=2023091320-chemist-dragonish-6874@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=stable@vger.kernel.org \
--cc=zengyhkyle@gmail.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;
as well as URLs for NNTP newsgroup(s).