From: patchwork-bot+netdevbpf@kernel.org
To: Song Liu <song@kernel.org>
Cc: bpf@vger.kernel.org, linux-security-module@vger.kernel.org,
linux-fsdevel@vger.kernel.org, fsverity@lists.linux.dev,
ebiggers@kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, martin.lau@linux.dev, brauner@kernel.org,
viro@zeniv.linux.org.uk, casey@schaufler-ca.com,
amir73il@gmail.com, kpsingh@kernel.org, roberto.sassu@huawei.com,
kernel-team@meta.com
Subject: Re: [PATCH v15 bpf-next 0/6] bpf: File verification with LSM and fsverity
Date: Sat, 02 Dec 2023 00:30:28 +0000 [thread overview]
Message-ID: <170147702831.23135.7635663186480885379.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231129234417.856536-1-song@kernel.org>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Wed, 29 Nov 2023 15:44:11 -0800 you wrote:
> Changes v14 => v15:
> 1. Fix selftest build without CONFIG_FS_VERITY. (Alexei)
> 2. Add Acked-by from KP.
>
> Changes v13 => v14:
> 1. Add "static" for bpf_fs_kfunc_set.
> 2. Add Acked-by from Christian Brauner.
>
> [...]
Here is the summary with links:
- [v15,bpf-next,1/6] bpf: Add kfunc bpf_get_file_xattr
https://git.kernel.org/bpf/bpf-next/c/ac9c05e0e453
- [v15,bpf-next,2/6] bpf, fsverity: Add kfunc bpf_get_fsverity_digest
https://git.kernel.org/bpf/bpf-next/c/67814c00de31
- [v15,bpf-next,3/6] Documentation/bpf: Add documentation for filesystem kfuncs
https://git.kernel.org/bpf/bpf-next/c/0de267d9ec65
- [v15,bpf-next,4/6] selftests/bpf: Sort config in alphabetic order
https://git.kernel.org/bpf/bpf-next/c/6b0ae4566aba
- [v15,bpf-next,5/6] selftests/bpf: Add tests for filesystem kfuncs
https://git.kernel.org/bpf/bpf-next/c/341f06fdddf7
- [v15,bpf-next,6/6] selftests/bpf: Add test that uses fsverity and xattr to sign a file
https://git.kernel.org/bpf/bpf-next/c/1030e9154258
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:[~2023-12-02 0:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 23:44 [PATCH v15 bpf-next 0/6] bpf: File verification with LSM and fsverity Song Liu
2023-11-29 23:44 ` [PATCH v15 bpf-next 1/6] bpf: Add kfunc bpf_get_file_xattr Song Liu
2023-11-29 23:44 ` [PATCH v15 bpf-next 2/6] bpf, fsverity: Add kfunc bpf_get_fsverity_digest Song Liu
2023-11-29 23:44 ` [PATCH v15 bpf-next 3/6] Documentation/bpf: Add documentation for filesystem kfuncs Song Liu
2023-11-29 23:44 ` [PATCH v15 bpf-next 4/6] selftests/bpf: Sort config in alphabetic order Song Liu
2023-11-29 23:44 ` [PATCH v15 bpf-next 5/6] selftests/bpf: Add tests for filesystem kfuncs Song Liu
2023-11-29 23:44 ` [PATCH v15 bpf-next 6/6] selftests/bpf: Add test that uses fsverity and xattr to sign a file Song Liu
2023-12-02 0:30 ` 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=170147702831.23135.7635663186480885379.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=amir73il@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=brauner@kernel.org \
--cc=casey@schaufler-ca.com \
--cc=daniel@iogearbox.net \
--cc=ebiggers@kernel.org \
--cc=fsverity@lists.linux.dev \
--cc=kernel-team@meta.com \
--cc=kpsingh@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=roberto.sassu@huawei.com \
--cc=song@kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).