public inbox for linux-security-module@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: "André Draszik" <andre.draszik@linaro.org>,
	"Song Liu" <song@kernel.org>,
	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, jack@suse.cz, kpsingh@kernel.org,
	mattbobrowski@google.com, amir73il@gmail.com,
	gregkh@linuxfoundation.org, tj@kernel.org,
	daan.j.demeyer@gmail.com,
	"Will McVicker" <willmcvicker@google.com>,
	"Peter Griffin" <peter.griffin@linaro.org>,
	"Tudor Ambarus" <tudor.ambarus@linaro.org>,
	kernel-team@android.com
Subject: Re: [PATCH v3 bpf-next 1/4] kernfs: remove iattr_mutex
Date: Tue, 19 Aug 2025 12:05:58 +0200	[thread overview]
Message-ID: <20250819-tonstudio-abgas-7feaac93f501@brauner> (raw)
In-Reply-To: <8f53c544-fd4a-4526-957f-9264a36aead6@siemens.com>

> ...but it looks like v3 was merged as-is in the end, without this fixup.
> Is there some separate patch in the pipeline, or was this forgotten?

This is a result of the trees diverging which we discussed earlier.
I sent a fix.

  reply	other threads:[~2025-08-19 10:06 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-23  6:38 [PATCH v3 bpf-next 0/4] Introduce bpf_cgroup_read_xattr 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 [this message]
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

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=20250819-tonstudio-abgas-7feaac93f501@brauner \
    --to=brauner@kernel.org \
    --cc=amir73il@gmail.com \
    --cc=andre.draszik@linaro.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.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=jan.kiszka@siemens.com \
    --cc=kernel-team@android.com \
    --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=peter.griffin@linaro.org \
    --cc=song@kernel.org \
    --cc=tj@kernel.org \
    --cc=tudor.ambarus@linaro.org \
    --cc=viro@zeniv.linux.org.uk \
    --cc=willmcvicker@google.com \
    /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