From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, netdev@vger.kernel.org,
bpf@vger.kernel.org, "Ricardo Cañuelo Navarro" <rcn@igalia.com>,
"Alexei Starovoitov" <ast@kernel.org>,
"Andrii Nakryiko" <andrii@kernel.org>,
"Daniel Borkmann" <daniel@iogearbox.net>,
"David S. Miller" <davem@davemloft.net>,
"Jakub Kicinski" <kuba@kernel.org>,
"Jesper Dangaard Brouer" <hawk@kernel.org>,
"John Fastabend" <john.fastabend@gmail.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Toke Høiland-Jørgensen" <toke@kernel.org>
Subject: Re: [PATCH stable] xdp: Reset bpf_redirect_info before running a xdp's BPF prog.
Date: Mon, 17 Mar 2025 15:08:49 +0100 [thread overview]
Message-ID: <20250317140849.H4eSnqFl@linutronix.de> (raw)
In-Reply-To: <2025031733-collide-dad-203a@gregkh>
> > I added the commit introducing map redirects as the origin of the
> > problem which is v4.14-rc1. The code is a bit different there it seems
> > to work similar.
>
> What stable tree(s) is this for? Just 6.6.y? Why not older ones?
I didn't say just v6.6.y. The commit introducing the problem is in
v4.14-rc1 so I would say all the way down for the supported trees. Just
let me know if it does not apply for some of the older kernel.
> > Greg, feel free to decide if this is worth a CVE.
>
> That's not how CVEs are assigned :)
>
> If you want one, please read the in-tree documentation we have for that.
I don't need one but it is tempting to go through the new process :).
If it does not make your handling here easier (since you have two
different patches for one issue) there is no need for it from my side.
Thank you.
> thanks,
>
> greg k-h
Sebastian
next prev parent reply other threads:[~2025-03-17 14:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-17 13:38 [PATCH stable] xdp: Reset bpf_redirect_info before running a xdp's BPF prog Sebastian Andrzej Siewior
2025-03-17 13:44 ` Greg KH
2025-03-17 14:08 ` Sebastian Andrzej Siewior [this message]
2025-04-04 13:37 ` Sebastian Andrzej Siewior
-- strict thread matches above, loose matches on Subject: below --
2025-04-14 16:21 Sebastian Andrzej Siewior
2025-04-22 10:43 ` 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=20250317140849.H4eSnqFl@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=hawk@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rcn@igalia.com \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=toke@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;
as well as URLs for NNTP newsgroup(s).