From: Daniel Trujillo <datrujillo@nvidia.com>
To: "bot+bpf-ci@kernel.org" <bot+bpf-ci@kernel.org>,
"ast@kernel.org" <ast@kernel.org>,
"daniel@iogearbox.net" <daniel@iogearbox.net>,
"andrii@kernel.org" <andrii@kernel.org>,
"eddyz87@gmail.com" <eddyz87@gmail.com>,
"memxor@gmail.com" <memxor@gmail.com>,
"martin.lau@linux.dev" <martin.lau@linux.dev>,
"song@kernel.org" <song@kernel.org>,
"yonghong.song@linux.dev" <yonghong.song@linux.dev>,
"jolsa@kernel.org" <jolsa@kernel.org>,
"emil@etsalapatis.com" <emil@etsalapatis.com>,
"ihor.solodrai@linux.dev" <ihor.solodrai@linux.dev>,
"john.fastabend@gmail.com" <john.fastabend@gmail.com>,
"sdf@fomichev.me" <sdf@fomichev.me>,
"davem@davemloft.net" <davem@davemloft.net>,
"edumazet@kernel.org" <edumazet@kernel.org>,
"kuba@kernel.org" <kuba@kernel.org>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"horms@kernel.org" <horms@kernel.org>
Cc: "bpf@vger.kernel.org" <bpf@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"martin.lau@kernel.org" <martin.lau@kernel.org>,
"mason@kernel.org" <mason@kernel.org>
Subject: Re: [PATCH bpf] bpf: mask speculative out-of-bounds skb helper loads
Date: Fri, 13 Nov 2026 22:10:30 +0000 [thread overview]
Message-ID: <PH7PR12MB879438580EC303DBBC3EC0DBB27F2@PH7PR12MB8794.namprd12.prod.outlook.com> (raw)
In-Reply-To: <651acc6e21aae9067dd3b8ccce4aa38da032b57324836cc75a1fbaa959e2ef10@mail.kernel.org>
> Should convert_bpf_ld_abs() get the same treatment, or should the
> changelog explain why constant-offset loads are out of scope?
Thanks for pointing this out. This patch only hardens the helper fast
paths used by the leakage demonstrated with added CLFLUSH instrumentation.
The offsets for inline ABS/MSH loads are fixed by the installed filter,
so changing an offset requires replacing the filter. In the proposed
long-packet/short-packet scenario, the offset must also fit within the
training packet's linear data. Neither should prevent exploitation;
they should just make it less convenient. But I have not demonstrated
leakage through the inline ABS/MSH path experimentally, so I scoped this
patch to the demonstrated helper path.
Before deciding how/whether to harden the inline ABS/MSH path, I'd
appreciate the maintainers' views on it and on the patch as submitted.
next prev parent reply other threads:[~2026-11-13 22:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 20:15 Daniël Trujillo via B4 Relay
2026-11-13 20:46 ` bot+bpf-ci
2026-11-13 22:10 ` Daniel Trujillo [this message]
2026-11-13 23:50 ` Alexei Starovoitov
2026-11-14 2:50 ` Daniel Trujillo
2026-11-14 2:56 ` Alexei Starovoitov
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=PH7PR12MB879438580EC303DBBC3EC0DBB27F2@PH7PR12MB8794.namprd12.prod.outlook.com \
--to=datrujillo@nvidia.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bot+bpf-ci@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=eddyz87@gmail.com \
--cc=edumazet@kernel.org \
--cc=emil@etsalapatis.com \
--cc=horms@kernel.org \
--cc=ihor.solodrai@linux.dev \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@kernel.org \
--cc=martin.lau@linux.dev \
--cc=mason@kernel.org \
--cc=memxor@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
--cc=song@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
all inboxes | Powered by JetHome®