From: patchwork-bot+netdevbpf@kernel.org
To: Matt Bobrowski <mattbobrowski@google.com>
Cc: bpf@vger.kernel.org, kpsingh@kernel.org, ast@kernel.org,
daniel@iogearbox.net, andrii@kernel.org, martin.lau@linux.dev,
eddyz87@gmail.com, song@kernel.org, yonghong.song@linux.dev,
linux-security-module@vger.kernel.org, roberto.sassu@huawei.com
Subject: Re: [PATCH] bpf: add security_file_post_open() LSM hook to sleepable_lsm_hooks
Date: Fri, 21 Jun 2024 18:00:33 +0000 [thread overview]
Message-ID: <171899283370.11208.7190626414627047538.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240618192923.379852-1-mattbobrowski@google.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Tue, 18 Jun 2024 19:29:22 +0000 you wrote:
> The new generic LSM hook security_file_post_open() was recently added
> to the LSM framework in commit 8f46ff5767b0b ("security: Introduce
> file_post_open hook"). Let's proactively add this generic LSM hook to
> the sleepable_lsm_hooks BTF ID set, because I can't see there being
> any strong reasons not to, and it's only a matter of time before
> someone else comes around and asks for it to be there.
>
> [...]
Here is the summary with links:
- bpf: add security_file_post_open() LSM hook to sleepable_lsm_hooks
https://git.kernel.org/bpf/bpf-next/c/6ddf3a9abd9f
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:[~2024-06-21 18:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-18 19:29 [PATCH] bpf: add security_file_post_open() LSM hook to sleepable_lsm_hooks Matt Bobrowski
2024-06-18 19:44 ` Paul Moore
2024-06-21 17:58 ` Daniel Borkmann
2024-06-21 18:00 ` 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=171899283370.11208.7190626414627047538.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=kpsingh@kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=mattbobrowski@google.com \
--cc=roberto.sassu@huawei.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 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.