From: patchwork-bot+netdevbpf@kernel.org
To: Martin KaFai Lau <kafai@fb.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, kernel-team@fb.com, yhs@fb.com
Subject: Re: [PATCH bpf-next 0/2] bpf: Allow doing stack read with size larger than the earlier spilled reg
Date: Wed, 03 Nov 2021 15:00:11 +0000 [thread overview]
Message-ID: <163595161153.22644.6536061698592430689.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211102064528.315637-1-kafai@fb.com>
Hello:
This series was applied to bpf/bpf.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Mon, 1 Nov 2021 23:45:28 -0700 you wrote:
> This set fixes an issue that the verifier rejects a u64 stack read
> after an earlier u32 scalar spill. It is caused by the earlier commit
> that allows tracking the spilled u32 scalar reg.
>
> Martin KaFai Lau (2):
> bpf: Do not reject when the stack read size is different from the
> tracked scalar size
> bpf: selftest: verifier test on refill from a smaller spill
>
> [...]
Here is the summary with links:
- [bpf-next,1/2] bpf: Do not reject when the stack read size is different from the tracked scalar size
https://git.kernel.org/bpf/bpf/c/f30d4968e9ae
- [bpf-next,2/2] bpf: selftest: verifier test on refill from a smaller spill
https://git.kernel.org/bpf/bpf/c/c08455dec5ac
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:[~2021-11-03 15:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-02 6:45 [PATCH bpf-next 0/2] bpf: Allow doing stack read with size larger than the earlier spilled reg Martin KaFai Lau
2021-11-02 6:45 ` [PATCH bpf-next 1/2] bpf: Do not reject when the stack read size is different from the tracked scalar size Martin KaFai Lau
2021-11-02 13:45 ` Hengqi Chen
2021-11-02 15:59 ` Yonghong Song
2021-11-02 6:45 ` [PATCH bpf-next 2/2] bpf: selftest: verifier test on refill from a smaller spill Martin KaFai Lau
2021-11-02 15:59 ` Yonghong Song
2021-11-03 15:00 ` 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=163595161153.22644.6536061698592430689.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=kafai@fb.com \
--cc=kernel-team@fb.com \
--cc=yhs@fb.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