BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: memxor@gmail.com, ast@kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next 0/4] Misc BPF fixes from sashiko findings
Date: Thu, 09 Jul 2026 05:10:15 +0000	[thread overview]
Message-ID: <178357381539.3246569.1187552790538928711.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260708211537.371874-1-daniel@iogearbox.net>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Kumar Kartikeya Dwivedi <memxor@gmail.com>:

On Wed,  8 Jul 2026 23:15:33 +0200 you wrote:
> Addressing some misc/random findings from sashiko that are worth fixing
> which popped up as pre-existing issues while working on the signed BPF
> loader series.
> 
> Daniel Borkmann (4):
>   bpf: Fix vmlinux BTF prep race in bpf_get_btf_vmlinux
>   bpf: Give vmlinux BTF init its own mutex
>   bpf: Account insn_aux_data allocation in bpf_check
>   bpf: Account scratch buffer in bpf_prog_calc_tag
> 
> [...]

Here is the summary with links:
  - [bpf-next,1/4] bpf: Fix vmlinux BTF prep race in bpf_get_btf_vmlinux
    https://git.kernel.org/bpf/bpf-next/c/92863e678070
  - [bpf-next,2/4] bpf: Give vmlinux BTF init its own mutex
    https://git.kernel.org/bpf/bpf-next/c/5e5e94d87dea
  - [bpf-next,3/4] bpf: Account insn_aux_data allocation in bpf_check
    https://git.kernel.org/bpf/bpf-next/c/42560699a83d
  - [bpf-next,4/4] bpf: Account scratch buffer in bpf_prog_calc_tag
    https://git.kernel.org/bpf/bpf-next/c/ff755b600790

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



      parent reply	other threads:[~2026-07-09  5:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-08 21:15 [PATCH bpf-next 0/4] Misc BPF fixes from sashiko findings Daniel Borkmann
2026-07-08 21:15 ` [PATCH bpf-next 1/4] bpf: Fix vmlinux BTF prep race in bpf_get_btf_vmlinux Daniel Borkmann
2026-07-08 22:17   ` bot+bpf-ci
2026-07-08 21:15 ` [PATCH bpf-next 2/4] bpf: Give vmlinux BTF init its own mutex Daniel Borkmann
2026-07-08 21:15 ` [PATCH bpf-next 3/4] bpf: Account insn_aux_data allocation in bpf_check Daniel Borkmann
2026-07-08 21:15 ` [PATCH bpf-next 4/4] bpf: Account scratch buffer in bpf_prog_calc_tag Daniel Borkmann
2026-07-08 21:25   ` sashiko-bot
2026-07-09  5: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=178357381539.3246569.1187552790538928711.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=memxor@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