From: Christian Brauner <brauner@kernel.org>
To: Song Liu <song@kernel.org>
Cc: bpf@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, viro@zeniv.linux.org.uk,
jack@suse.cz, kernel-team@meta.com, andrii@kernel.org,
eddyz87@gmail.com, ast@kernel.org, daniel@iogearbox.net,
martin.lau@linux.dev, kpsingh@kernel.org,
mattbobrowski@google.com
Subject: Re: [PATCH bpf-next 0/2] security.bpf xattr name prefix
Date: Mon, 14 Oct 2024 12:18:02 +0200 [thread overview]
Message-ID: <20241014-zeigt-nachwachsen-ef41e225b73c@brauner> (raw)
In-Reply-To: <CAPhsuW6nv=-wEaoPxB_+VQTkfnvYzBtfjbrg2EeNK7jjN6V83g@mail.gmail.com>
On Fri, Oct 11, 2024 at 10:40:02AM -0700, Song Liu wrote:
> Hi Christian, Al, and Jan,
>
> Could you please review and share your comments on this set?
Yes, as I said in-person, I think adding security.bpf is fine.
prev parent reply other threads:[~2024-10-14 10:18 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-02 21:46 Song Liu
2024-10-02 21:46 ` [PATCH bpf-next 1/2] fs/xattr: bpf: Introduce " Song Liu
2024-10-07 8:39 ` Jiri Olsa
2024-10-07 17:15 ` Song Liu
2024-10-14 10:18 ` Christian Brauner
2024-10-02 21:46 ` [PATCH bpf-next 2/2] selftests/bpf: Extend test fs_kfuncs to cover security.bpf xattr names Song Liu
2024-10-15 5:07 ` Christoph Hellwig
2024-10-15 5:21 ` Song Liu
2024-10-15 5:25 ` Christoph Hellwig
2024-10-15 5:52 ` Song Liu
2024-10-15 6:42 ` Christoph Hellwig
2024-10-15 13:54 ` Song Liu
2024-10-16 7:49 ` Christoph Hellwig
2024-10-16 13:51 ` Jan Kara
2024-10-16 14:51 ` Christian Brauner
2024-10-16 16:38 ` Song Liu
2024-10-17 15:03 ` Christoph Hellwig
2024-10-21 13:24 ` Christian Brauner
2024-10-23 6:45 ` Christoph Hellwig
2024-10-30 20:44 ` Song Liu
2024-10-31 6:56 ` Christoph Hellwig
2024-10-31 15:56 ` Song Liu
2024-10-31 16:10 ` Alexei Starovoitov
2024-10-11 17:40 ` [PATCH bpf-next 0/2] security.bpf xattr name prefix Song Liu
2024-10-14 10:18 ` Christian Brauner [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=20241014-zeigt-nachwachsen-ef41e225b73c@brauner \
--to=brauner@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=jack@suse.cz \
--cc=kernel-team@meta.com \
--cc=kpsingh@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=mattbobrowski@google.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
all inboxes | Powered by JetHome®