public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Andrii Nakryiko <andrii@kernel.org>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
	kernel-team@fb.com
Subject: Re: [PATCH v2 bpf-next 0/3] Fix BPF verifier global subprog context argument logic
Date: Fri, 17 Feb 2023 20:30:17 +0000	[thread overview]
Message-ID: <167666581776.8842.4868500111566161313.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230216045954.3002473-1-andrii@kernel.org>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:

On Wed, 15 Feb 2023 20:59:51 -0800 you wrote:
> Fix kernel bug in determining whether global subprog's argument is PTR_TO_CTX,
> which is done based on type names. Currently KPROBE programs are broken.
> 
> Add few tests validating that KPROBE context can be passed to global subprog.
> For that also refactor test_global_funcs test to use test_loader framework.
> 
> v1->v2:
>   - fix compilation warning on arm64 and s390x by force-casting ctx to
>     `void *`, to discard const from `const struct user_pt_regs *`, when
>     passing it to bpf_get_stack().
> 
> [...]

Here is the summary with links:
  - [v2,bpf-next,1/3] bpf: fix global subprog context argument resolution logic
    https://git.kernel.org/bpf/bpf-next/c/d384dce281ed
  - [v2,bpf-next,2/3] selftests/bpf: convert test_global_funcs test to test_loader framework
    https://git.kernel.org/bpf/bpf-next/c/95ebb376176c
  - [v2,bpf-next,3/3] selftests/bpf: add global subprog context passing tests
    https://git.kernel.org/bpf/bpf-next/c/e2b5cfc978f8

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-02-17 20:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-16  4:59 [PATCH v2 bpf-next 0/3] Fix BPF verifier global subprog context argument logic Andrii Nakryiko
2023-02-16  4:59 ` [PATCH v2 bpf-next 1/3] bpf: fix global subprog context argument resolution logic Andrii Nakryiko
2023-02-16  4:59 ` [PATCH v2 bpf-next 2/3] selftests/bpf: convert test_global_funcs test to test_loader framework Andrii Nakryiko
2023-02-16  4:59 ` [PATCH v2 bpf-next 3/3] selftests/bpf: add global subprog context passing tests Andrii Nakryiko
2023-02-17 20:24   ` Daniel Borkmann
2023-02-16 17:40 ` [PATCH v2 bpf-next 0/3] Fix BPF verifier global subprog context argument logic Stanislav Fomichev
2023-02-16 19:53   ` Andrii Nakryiko
2023-02-17 20:30 ` 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=167666581776.8842.4868500111566161313.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=kernel-team@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