From: patchwork-bot+netdevbpf@kernel.org
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: memxor@gmail.com, paul@paul-moore.com, bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next] bpf: Fix security_bpf_map_create error handling
Date: Thu, 09 Jul 2026 08:20:05 +0000 [thread overview]
Message-ID: <178358520589.3322995.17637812506485356697.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260709073422.379247-1-daniel@iogearbox.net>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Kumar Kartikeya Dwivedi <memxor@gmail.com>:
On Thu, 9 Jul 2026 09:34:22 +0200 you wrote:
> Commit 5816bf4273ed ("lsm,selinux: Add LSM blob support for BPF objects")
> made the LSM hook wrappers for BPF object creation clean up the LSM
> state internally upon denial, e.g. security_bpf_map_create() internally
> calls security_bpf_map_free() when the bpf_map_create hook returns an
> error. map_create() however still routes a denial to its free_map_sec
> label, which invokes security_bpf_map_free() a second time, so the
> bpf_map_free hook fires twice for a single denied map.
>
> [...]
Here is the summary with links:
- [bpf-next] bpf: Fix security_bpf_map_create error handling
https://git.kernel.org/bpf/bpf-next/c/36ffa86c42f9
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-09 8:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 7:34 [PATCH bpf-next] bpf: Fix security_bpf_map_create error handling Daniel Borkmann
2026-07-09 7:48 ` sashiko-bot
2026-07-09 7:49 ` Daniel Borkmann
2026-07-09 8: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=178358520589.3322995.17637812506485356697.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=memxor@gmail.com \
--cc=paul@paul-moore.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.