From: patchwork-bot+netdevbpf@kernel.org
To: Andrei Matei <andreimatei1@gmail.com>
Cc: bpf@vger.kernel.org, sunhao.th@gmail.com,
andrii.nakryiko@gmail.com, eddyz87@gmail.com
Subject: Re: [PATCH bpf v5 0/3] bpf: fix accesses to uninit stack slots
Date: Fri, 08 Dec 2023 23:10:24 +0000 [thread overview]
Message-ID: <170207702469.20219.7388621141536966920.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231208032519.260451-1-andreimatei1@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Thu, 7 Dec 2023 22:25:16 -0500 you wrote:
> Fix two related issues issues around verifying stack accesses:
> 1. accesses to uninitialized stack memory was allowed inconsistently
> 2. the maximum stack depth needed for a program was not always
> maintained correctly
>
> The two issues are fixed together in one commit because the code for one
> affects the other.
>
> [...]
Here is the summary with links:
- [bpf-next,v5,1/3] bpf: add some comments to stack representation
https://git.kernel.org/bpf/bpf-next/c/92e1567ee3e3
- [bpf-next,v5,2/3] bpf: fix accesses to uninit stack slots
https://git.kernel.org/bpf/bpf-next/c/6b4a64bafd10
- [bpf-next,v5,3/3] bpf: minor cleanup around stack bounds
https://git.kernel.org/bpf/bpf-next/c/2929bfac006d
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:[~2023-12-08 23:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-08 3:25 [PATCH bpf v5 0/3] bpf: fix accesses to uninit stack slots Andrei Matei
2023-12-08 3:25 ` [PATCH bpf-next v5 1/3] bpf: add some comments to stack representation Andrei Matei
2023-12-08 21:06 ` Eduard Zingerman
2023-12-08 3:25 ` [PATCH bpf-next v5 2/3] bpf: fix accesses to uninit stack slots Andrei Matei
2023-12-08 3:25 ` [PATCH bpf-next v5 3/3] bpf: minor cleanup around stack bounds Andrei Matei
2023-12-08 21:10 ` Eduard Zingerman
2023-12-08 23:10 ` 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=170207702469.20219.7388621141536966920.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andreimatei1@gmail.com \
--cc=andrii.nakryiko@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=eddyz87@gmail.com \
--cc=sunhao.th@gmail.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