mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Song Liu <song@kernel.org>
Cc: bpf@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-security-module@vger.kernel.org, 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, amir73il@gmail.com,
	gregkh@linuxfoundation.org, tj@kernel.org,
	daan.j.demeyer@gmail.com
Subject: Re: [PATCH v3 bpf-next 0/4] Introduce bpf_cgroup_read_xattr
Date: Fri, 27 Jun 2025 02:20:10 +0000	[thread overview]
Message-ID: <175099081075.1402944.15924179208170467292.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250623063854.1896364-1-song@kernel.org>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Christian Brauner <brauner@kernel.org>:

On Sun, 22 Jun 2025 23:38:50 -0700 you wrote:
> Introduce a new kfunc bpf_cgroup_read_xattr, which can read xattr from
> cgroupfs nodes. The primary users are LSMs, cgroup programs, and sched_ext.
> 
> ---
> 
> Changes v2 => v3:
> 1. Make bpf_cgroup_read_xattr available to all program types.
> 2. Fix gcc build warning on the selftests.
> 3. Add "ifdef CONFIG_CGROUPS" around bpf_cgroup_read_xattr.
> 
> [...]

Here is the summary with links:
  - [v3,bpf-next,1/4] kernfs: remove iattr_mutex
    (no matching commit)
  - [v3,bpf-next,2/4] bpf: Introduce bpf_cgroup_read_xattr to read xattr of cgroup's node
    https://git.kernel.org/bpf/bpf-next/c/535b070f4a80
  - [v3,bpf-next,3/4] bpf: Mark cgroup_subsys_state->cgroup RCU safe
    https://git.kernel.org/bpf/bpf-next/c/1504d8c7c702
  - [v3,bpf-next,4/4] selftests/bpf: Add tests for bpf_cgroup_read_xattr
    https://git.kernel.org/bpf/bpf-next/c/f4fba2d6d282

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2025-06-27  2:19 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-23  6:38 Song Liu
2025-06-23  6:38 ` [PATCH v3 bpf-next 1/4] kernfs: remove iattr_mutex Song Liu
2025-07-02 10:47   ` André Draszik
2025-07-02 12:17     ` Christian Brauner
2025-07-03  6:28       ` André Draszik
2025-08-16  5:52       ` Jan Kiszka
2025-08-19 10:05         ` Christian Brauner
2025-06-23  6:38 ` [PATCH v3 bpf-next 2/4] bpf: Introduce bpf_cgroup_read_xattr to read xattr of cgroup's node Song Liu
2025-06-23  6:38 ` [PATCH v3 bpf-next 3/4] bpf: Mark cgroup_subsys_state->cgroup RCU safe Song Liu
2025-06-23  6:38 ` [PATCH v3 bpf-next 4/4] selftests/bpf: Add tests for bpf_cgroup_read_xattr Song Liu
2025-06-23 11:03 ` [PATCH v3 bpf-next 0/4] Introduce bpf_cgroup_read_xattr Christian Brauner
2025-06-27  2:14   ` Alexei Starovoitov
2025-06-27  4:04     ` Song Liu
2025-06-27 15:59       ` Alexei Starovoitov
2025-06-27 16:20         ` Song Liu
2025-07-01  8:32           ` Christian Brauner
2025-07-01 16:23             ` Song Liu
2025-07-02 12:19               ` Christian Brauner
2025-07-01  8:31     ` Christian Brauner
2025-07-01 14:51       ` Alexei Starovoitov
2025-07-02  8:37         ` Christian Brauner
2025-06-27  2: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=175099081075.1402944.15924179208170467292.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=daan.j.demeyer@gmail.com \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --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=linux-security-module@vger.kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=mattbobrowski@google.com \
    --cc=song@kernel.org \
    --cc=tj@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®