All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Kuniyuki Iwashima <kuniyu@google.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
	dxu@dxuuu.xyz, pablo@netfilter.org, kadlec@netfilter.org,
	fw@strlen.de, kuni1840@gmail.com, bpf@vger.kernel.org,
	netdev@vger.kernel.org, netfilter-devel@vger.kernel.org,
	syzbot+40f772d37250b6d10efc@syzkaller.appspotmail.com
Subject: Re: [PATCH v2 bpf] bpf: Disable migration in nf_hook_run_bpf().
Date: Thu, 24 Jul 2025 02:10:05 +0000	[thread overview]
Message-ID: <175332300576.1847444.11963207848328088857.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250722224041.112292-1-kuniyu@google.com>

Hello:

This patch was applied to bpf/bpf-next.git (net)
by Martin KaFai Lau <martin.lau@kernel.org>:

On Tue, 22 Jul 2025 22:40:37 +0000 you wrote:
> syzbot reported that the netfilter bpf prog can be called without
> migration disabled in xmit path.
> 
> Then the assertion in __bpf_prog_run() fails, triggering the splat
> below. [0]
> 
> Let's use bpf_prog_run_pin_on_cpu() in nf_hook_run_bpf().
> 
> [...]

Here is the summary with links:
  - [v2,bpf] bpf: Disable migration in nf_hook_run_bpf().
    https://git.kernel.org/bpf/bpf-next/c/17ce3e5949bc

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



      parent reply	other threads:[~2025-07-24  2:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-22 22:40 [PATCH v2 bpf] bpf: Disable migration in nf_hook_run_bpf() Kuniyuki Iwashima
2025-07-22 23:03 ` Florian Westphal
2025-07-24  2: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=175332300576.1847444.11963207848328088857.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=dxu@dxuuu.xyz \
    --cc=fw@strlen.de \
    --cc=kadlec@netfilter.org \
    --cc=kuni1840@gmail.com \
    --cc=kuniyu@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pablo@netfilter.org \
    --cc=syzbot+40f772d37250b6d10efc@syzkaller.appspotmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.