All of lore.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@zeniv.linux.org.uk>
To: Christian Brauner <brauner@kernel.org>
Cc: linux-fsdevel@vger.kernel.org, "Jan Kara" <jack@suse.cz>,
	"Jeff Layton" <jlayton@kernel.org>,
	"Amir Goldstein" <amir73il@gmail.com>,
	"Lennart Poettering" <lennart@poettering.net>,
	"Zbigniew Jędrzejewski-Szmek" <zbyszek@in.waw.pl>,
	"Josef Bacik" <josef@toxicpanda.com>
Subject: Re: [PATCH 3/3] fs: add immutable rootfs
Date: Tue, 6 Jan 2026 22:59:17 +0000	[thread overview]
Message-ID: <20260106225917.GL1712166@ZenIV> (raw)
In-Reply-To: <20260106-verpachten-antrag-5b610d1ec4d0@brauner>

On Tue, Jan 06, 2026 at 11:07:32PM +0100, Christian Brauner wrote:

> 
> Afaict, FS_IMMUTABLE_FL can be cleared by a sufficiently privileged
> process breaking the promise that this is a permanently immutable
> rootfs.

Not on ramfs:

int vfs_fileattr_set(struct mnt_idmap *idmap, struct dentry *dentry,
                     struct file_kattr *fa)
{
        struct inode *inode = d_inode(dentry);
        struct file_kattr old_ma = {};
        int err;
 
        if (!inode->i_op->fileattr_set)
                return -ENOIOCTLCMD;

and that's it, priveleges do not matter.

  reply	other threads:[~2026-01-06 22:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-02 14:36 [PATCH 0/3] fs: add immutable rootfs and support pivot_root() in the initramfs Christian Brauner
2026-01-02 14:36 ` [PATCH 1/3] fs: ensure that internal tmpfs mount gets mount id zero Christian Brauner
2026-01-02 14:36 ` [PATCH 2/3] fs: add init_pivot_root() Christian Brauner
2026-01-02 14:36 ` [PATCH 3/3] fs: add immutable rootfs Christian Brauner
2026-01-04  7:27   ` Al Viro
2026-01-04  7:41     ` Al Viro
2026-01-06 22:07       ` Christian Brauner
2026-01-06 22:59         ` Al Viro [this message]
2026-01-07 10:53           ` Christian Brauner
2026-01-07  2:28   ` Gao Xiang
2026-01-07  2:47     ` Al Viro
2026-01-07  2:55       ` Gao Xiang
2026-01-07 10:52       ` Christian Brauner
2026-01-07 16:33         ` Colin Walters
2026-01-08 11:02           ` Christian Brauner
2026-01-25 20:47             ` Askar Safin

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=20260106225917.GL1712166@ZenIV \
    --to=viro@zeniv.linux.org.uk \
    --cc=amir73il@gmail.com \
    --cc=brauner@kernel.org \
    --cc=jack@suse.cz \
    --cc=jlayton@kernel.org \
    --cc=josef@toxicpanda.com \
    --cc=lennart@poettering.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.