From: Greg KH <greg@kroah.com>
To: Martin KaFai Lau <martin.lau@linux.dev>
Cc: Jason Xing <kerneljasonxing@gmail.com>,
stable@vger.kernel.org, stable-commits@vger.kernel.org,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Eduard Zingerman <eddyz87@gmail.com>, Song Liu <song@kernel.org>,
Yonghong Song <yonghong.song@linux.dev>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@fomichev.me>, Hao Luo <haoluo@google.com>,
Jiri Olsa <jolsa@kernel.org>, Eric Dumazet <edumazet@google.com>,
Neal Cardwell <ncardwell@google.com>,
Kuniyuki Iwashima <kuniyu@amazon.com>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>, David Ahern <dsahern@kernel.org>
Subject: Re: Patch "bpf: Prevent unsafe access to the sock fields in the BPF timestamping callback" has been added to the 6.1-stable tree
Date: Tue, 27 May 2025 16:53:38 +0200 [thread overview]
Message-ID: <2025052729-uphold-punctuate-1b57@gregkh> (raw)
In-Reply-To: <69d1a996-5eaa-4af9-978d-c59c70a95438@linux.dev>
On Fri, May 23, 2025 at 04:17:21PM -0700, Martin KaFai Lau wrote:
> On 5/22/25 4:25 PM, Jason Xing wrote:
> > On Fri, May 23, 2025 at 7:17 AM Sasha Levin <sashal@kernel.org> wrote:
> > >
> > > This is a note to let you know that I've just added the patch titled
> > >
> > > bpf: Prevent unsafe access to the sock fields in the BPF timestamping callback
> > >
> > > to the 6.1-stable tree which can be found at:
> > > http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> > >
> > > The filename of the patch is:
> > > bpf-prevent-unsafe-access-to-the-sock-fields-in-the-.patch
> > > and it can be found in the queue-6.1 subdirectory.
> > >
> > > If you, or anyone else, feels it should not be added to the stable tree,
> > > please let <stable@vger.kernel.org> know about it.
> >
> > Hi,
> >
> > I'm notified that this patch has been added into many branches, which
> > is against my expectations. The BPF timestaping feature was
> > implemented in 6.14 and the patch you are handling is just one of them.
> >
> > The function of this patch prevents unexpected bpf programs using this
> > feature from triggering
> > fatal problems. So, IMHO, we don't need this patch in all the
> > older/stable branches:)
> >
> > Thanks,
> > Jason
> >
> >
> > >
> > >
> > >
> > > commit 00b709040e0fdf5949dfbf02f38521e0b10943ac
> > > Author: Jason Xing <kerneljasonxing@gmail.com>
> > > Date: Thu Feb 20 15:29:31 2025 +0800
> > >
> > > bpf: Prevent unsafe access to the sock fields in the BPF timestamping callback
> > >
> > > [ Upstream commit fd93eaffb3f977b23bc0a48d4c8616e654fcf133 ]
> > >
> > > The subsequent patch will implement BPF TX timestamping. It will
>
> Agree. The patch is a preparation work for the new bpf tx timestamping
> feature. It is not stable material.
Dropped from everywhere, thanks.
greg k-h
prev parent reply other threads:[~2025-05-27 14:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250522231656.3254864-1-sashal@kernel.org>
2025-05-22 23:25 ` Patch "bpf: Prevent unsafe access to the sock fields in the BPF timestamping callback" has been added to the 6.1-stable tree Jason Xing
2025-05-23 23:17 ` Martin KaFai Lau
2025-05-27 14:53 ` Greg KH [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=2025052729-uphold-punctuate-1b57@gregkh \
--to=greg@kroah.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=eddyz87@gmail.com \
--cc=edumazet@google.com \
--cc=haoluo@google.com \
--cc=horms@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kerneljasonxing@gmail.com \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.com \
--cc=martin.lau@linux.dev \
--cc=ncardwell@google.com \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=yonghong.song@linux.dev \
/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