From: Christian Brauner <brauner@kernel.org>
To: linux-fsdevel@vger.kernel.org
Cc: "Jann Horn" <jannh@google.com>,
"Josef Bacik" <josef@toxicpanda.com>,
"Jeff Layton" <jlayton@kernel.org>,
"Daan De Meyer" <daan.j.demeyer@gmail.com>,
"Lennart Poettering" <lennart@poettering.net>,
"Mike Yuan" <me@yhndnzj.com>,
"Zbigniew Jędrzejewski-Szmek" <zbyszek@in.waw.pl>,
"Christian Brauner" <brauner@kernel.org>,
"Alexander Mikhalitsyn" <alexander@mihalicyn.com>
Subject: [PATCH RFC 3/9] libfs: prepare to allow for non-immutable pidfd inodes
Date: Tue, 17 Jun 2025 17:42:11 +0200 [thread overview]
Message-ID: <20250617-work-pidfs-xattr-v1-3-2d0df10405bb@kernel.org> (raw)
In-Reply-To: <20250617-work-pidfs-xattr-v1-0-2d0df10405bb@kernel.org>
Allow for S_IMMUTABLE to be stripped so that we can support xattrs on
pidfds.
Signed-off-by: Christian Brauner <brauner@kernel.org>
---
fs/libfs.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/fs/libfs.c b/fs/libfs.c
index f496373869fb..9098dc6b26f9 100644
--- a/fs/libfs.c
+++ b/fs/libfs.c
@@ -2162,7 +2162,6 @@ static struct dentry *prepare_anon_dentry(struct dentry **stashed,
/* Notice when this is changed. */
WARN_ON_ONCE(!S_ISREG(inode->i_mode));
- WARN_ON_ONCE(!IS_IMMUTABLE(inode));
dentry = d_alloc_anon(sb);
if (!dentry) {
--
2.47.2
next prev parent reply other threads:[~2025-06-17 15:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-17 15:42 [PATCH RFC 0/9] pidfs: support extended attributes Christian Brauner
2025-06-17 15:42 ` [PATCH RFC 1/9] pidfs: keep pidfs dentry stashed once created Christian Brauner
2025-06-18 19:34 ` Alexander Mikhalitsyn
2025-06-17 15:42 ` [PATCH RFC 2/9] pidfs: remove pidfs_pid_valid() Christian Brauner
2025-06-18 19:40 ` Alexander Mikhalitsyn
2025-06-17 15:42 ` Christian Brauner [this message]
2025-06-17 15:42 ` [PATCH RFC 4/9] pidfs: make inodes mutable 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=20250617-work-pidfs-xattr-v1-3-2d0df10405bb@kernel.org \
--to=brauner@kernel.org \
--cc=alexander@mihalicyn.com \
--cc=daan.j.demeyer@gmail.com \
--cc=jannh@google.com \
--cc=jlayton@kernel.org \
--cc=josef@toxicpanda.com \
--cc=lennart@poettering.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=me@yhndnzj.com \
--cc=zbyszek@in.waw.pl \
/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 NNTP newsgroup(s).