public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Song Liu <song@kernel.org>
To: bpf@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org
Cc: kernel-team@meta.com, andrii@kernel.org, eddyz87@gmail.com,
	ast@kernel.org, daniel@iogearbox.net, martin.lau@linux.dev,
	viro@zeniv.linux.org.uk, brauner@kernel.org, jack@suse.cz,
	kpsingh@kernel.org, mattbobrowski@google.com,
	Song Liu <song@kernel.org>
Subject: [PATCH bpf-next 0/2] security.bpf xattr name prefix
Date: Wed,  2 Oct 2024 14:46:35 -0700	[thread overview]
Message-ID: <20241002214637.3625277-1-song@kernel.org> (raw)

Follow up discussion in LPC 2024 [1], that we need security.bpf xattr
prefix. This set adds "security.bpf" xattr name prefix, and allows
bpf kfuncs bpf_get_[file|dentry]_xattr() to read these xattrs.


[1] https://lpc.events/event/18/contributions/1940/

Song Liu (2):
  fs/xattr: bpf: Introduce security.bpf xattr name prefix
  selftests/bpf: Extend test fs_kfuncs to cover security.bpf xattr names

 fs/bpf_fs_kfuncs.c                            | 19 ++++++++-
 include/uapi/linux/xattr.h                    |  4 ++
 .../selftests/bpf/prog_tests/fs_kfuncs.c      | 40 ++++++++++++++-----
 .../selftests/bpf/progs/test_get_xattr.c      | 30 ++++++++++++--
 4 files changed, 78 insertions(+), 15 deletions(-)

--
2.43.5

             reply	other threads:[~2024-10-02 21:47 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-02 21:46 Song Liu [this message]
2024-10-02 21:46 ` [PATCH bpf-next 1/2] fs/xattr: bpf: Introduce security.bpf xattr name prefix 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

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=20241002214637.3625277-1-song@kernel.org \
    --to=song@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=brauner@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=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