From: patchwork-bot+netdevbpf@kernel.org
To: Nuoqi Gui <gnq25@mails.tsinghua.edu.cn>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
eddyz87@gmail.com, memxor@gmail.com, john.fastabend@gmail.com,
martin.lau@linux.dev, luis.gerhorst@fau.de, shuah@kernel.org,
bpf@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org, jiayuan.chen@linux.dev,
emil@etsalapatis.com
Subject: Re: [PATCH bpf v3 0/2] bpf: Fix stack slot index for Spectre v4 nospec checks
Date: Mon, 22 Jun 2026 01:07:06 +0000 [thread overview]
Message-ID: <178209042679.554493.16748055730753195339.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260618-f01-11-stack-nospec-slot-index-v3-0-780297041721@mails.tsinghua.edu.cn>
Hello:
This series was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Thu, 18 Jun 2026 01:50:25 +0800 you wrote:
> check_stack_write_fixed_off() uses one byte-indexing scheme when checking
> whether a fixed-offset stack write needs Spectre v4 sanitization, and another
> scheme when recording the write into slot_type[].
>
> For sub-8-byte writes this can make the sanitization check look at bytes that
> are not overwritten by the write. A zeroed lower half-slot followed by a write
> to the upper half-slot can therefore miss the nospec barrier for the second
> write.
>
> [...]
Here is the summary with links:
- [bpf,v3,1/2] bpf: Fix stack slot index in nospec checks
https://git.kernel.org/bpf/bpf/c/d1d53aa30ab3
- [bpf,v3,2/2] selftests/bpf: Cover stack nospec slot indexing
https://git.kernel.org/bpf/bpf/c/a93ae7ed5972
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-06-22 1:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-17 17:50 [PATCH bpf v3 0/2] bpf: Fix stack slot index for Spectre v4 nospec checks Nuoqi Gui
2026-06-17 17:50 ` [PATCH bpf v3 1/2] bpf: Fix stack slot index in " Nuoqi Gui
2026-06-17 17:50 ` [PATCH bpf v3 2/2] selftests/bpf: Cover stack nospec slot indexing Nuoqi Gui
2026-06-22 1:07 ` patchwork-bot+netdevbpf [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=178209042679.554493.16748055730753195339.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=gnq25@mails.tsinghua.edu.cn \
--cc=jiayuan.chen@linux.dev \
--cc=john.fastabend@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=luis.gerhorst@fau.de \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=shuah@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.