BPF List
 help / color / mirror / Atom feed
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-next v5 0/3] bpf: fix verification of indirect var-off stack access
Date: Thu, 07 Dec 2023 19:10:24 +0000	[thread overview]
Message-ID: <170197622464.16032.7891344511842639576.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231207041150.229139-1-andreimatei1@gmail.com>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:

On Wed,  6 Dec 2023 23:11:47 -0500 you wrote:
> V4 to V5:
>   - split the test into a separate patch
> 
> V3 to V4:
>   - include a test per Eduard's request
>   - target bpf-next per Alexei's request (patches didn't change)
> 
> [...]

Here is the summary with links:
  - [bpf-next,v5,1/3] bpf: fix verification of indirect var-off stack access
    https://git.kernel.org/bpf/bpf-next/c/4f114bc280bb
  - [bpf-next,v5,2/3] bpf: add verifier regression test for previous patch
    https://git.kernel.org/bpf/bpf-next/c/ec32ca301faa
  - [bpf-next,v5,3/3] bpf: guard stack limits against 32bit overflow
    https://git.kernel.org/bpf/bpf-next/c/755f82668d81

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2023-12-07 19:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-07  4:11 [PATCH bpf-next v5 0/3] bpf: fix verification of indirect var-off stack access Andrei Matei
2023-12-07  4:11 ` [PATCH bpf-next v5 1/3] " Andrei Matei
2023-12-07  4:11 ` [PATCH bpf-next v5 2/3] bpf: add verifier regression test for previous patch Andrei Matei
2023-12-07  4:11 ` [PATCH bpf-next v5 3/3] bpf: guard stack limits against 32bit overflow Andrei Matei
2023-12-07 19: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=170197622464.16032.7891344511842639576.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