From: patchwork-bot+netdevbpf@kernel.org
To: Sechang Lim <rhkrqnwk98@gmail.com>
Cc: kpsingh@kernel.org, mattbobrowski@google.com, ast@kernel.org,
daniel@iogearbox.net, andrii@kernel.org, eddyz87@gmail.com,
memxor@gmail.com, martin.lau@linux.dev, song@kernel.org,
yonghong.song@linux.dev, jolsa@kernel.org, paul@paul-moore.com,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf v2] bpf,lsm: drop bpf_prog_free from sleepable_lsm_hooks
Date: Wed, 01 Jul 2026 20:20:05 +0000 [thread overview]
Message-ID: <178293720565.1283177.10375180205775376810.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260701080757.1394144-1-rhkrqnwk98@gmail.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Wed, 1 Jul 2026 08:07:51 +0000 you wrote:
> __bpf_prog_put_rcu() is the call_rcu() callback for non-sleepable programs.
> security_bpf_prog_free() called from there fires bpf_prog_free in softirq;
> if a sleepable LSM prog is attached to that hook, might_fault() BUGs:
>
> BUG: sleeping function called from invalid context
> in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 5038
> preempt_count: 101, expected: 0
> Call Trace:
> <IRQ>
> __bpf_prog_enter_sleepable+0x1cd/0x320 kernel/bpf/trampoline.c:1255
> bpf_trampoline_6442549705+0x53/0xd7
> security_bpf_prog_free+0xde/0x130 security/security.c:5465
> __bpf_prog_put_rcu+0xab/0xd0 kernel/bpf/syscall.c:2365
> rcu_do_batch kernel/rcu/tree.c:2617 [inline]
> handle_softirqs+0x236/0x800 kernel/softirq.c:622
> </IRQ>
>
> [...]
Here is the summary with links:
- [bpf,v2] bpf,lsm: drop bpf_prog_free from sleepable_lsm_hooks
https://git.kernel.org/bpf/bpf-next/c/2ce3f548cfc6
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:[~2026-07-01 20:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-01 8:07 [PATCH bpf v2] bpf,lsm: drop bpf_prog_free from sleepable_lsm_hooks Sechang Lim
2026-07-01 20:20 ` 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=178293720565.1283177.10375180205775376810.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=eddyz87@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=mattbobrowski@google.com \
--cc=memxor@gmail.com \
--cc=paul@paul-moore.com \
--cc=rhkrqnwk98@gmail.com \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
/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