public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Oleksandr Natalenko <oleksandr@natalenko.name>
Cc: linux-kernel@vger.kernel.org, linux-xfs@vger.kernel.org,
	Carlos Maiolino <cem@kernel.org>,
	Pavel Reichl <preichl@redhat.com>,
	Vlastimil Babka <vbabka@suse.cz>,
	Thorsten Leemhuis <linux@leemhuis.info>
Subject: Re: XFS attr2 mount option removal may break system boot
Date: Mon, 13 Oct 2025 14:29:53 -0700	[thread overview]
Message-ID: <20251013212953.GP6188@frogsfrogsfrogs> (raw)
In-Reply-To: <3654080.iIbC2pHGDl@natalenko.name>

On Mon, Oct 13, 2025 at 09:08:38PM +0200, Oleksandr Natalenko wrote:
> Hello.
> 
> In v6.18, the attr2 XFS mount option is removed. This may silently break system boot if the attr2 option is still present in /etc/fstab for rootfs.
> 
> Consider Arch Linux that is being set up from scratch with / being
> formatted as XFS. The genfstab command that is used to generate
> /etc/fstab produces something like this by default:
> 
> /dev/sda2 on / type xfs (rw,relatime,attr2,discard,inode64,logbufs=8,logbsize=32k,noquota)

As in, /etc/fstab captures ALL the output of /proc/mounts, including the
strings that reflect filesystem state even if not explicitly provided by
whoever mounted the fs?  Is your actual fstab contents:

/dev/sda2	/	relatime,attr2,discard,inode64,logbufs=8,logbsize=32k,noquota	0	0

(aka logbufs/inode64/logbsize/sunit/swidth and the ones the vfs puts in
there on its own)

That's pretty messed up, but open-parsing stringly typed data structures
with unclear RMW semantics is always going to be a trash fire.

> Once the system is set up and rebooted, there's no deprecation warning seen in the kernel log:
> 
> # cat /proc/cmdline
> root=UUID=77b42de2-397e-47ee-a1ef-4dfd430e47e9 rootflags=discard rd.luks.options=discard quiet
> 
> # dmesg | grep -i xfs
> [    2.409818] SGI XFS with ACLs, security attributes, realtime, scrub, repair, quota, no debug enabled
> [    2.415341] XFS (sda2): Mounting V5 Filesystem 77b42de2-397e-47ee-a1ef-4dfd430e47e9
> [    2.442546] XFS (sda2): Ending clean mount
> 
> Although as per the deprecation intention, it should be there.
> 
> Vlastimil (in Cc) suggests this is because xfs_fs_warn_deprecated() doesn't produce any warning by design if the XFS FS is set to be rootfs and gets remounted read-write during boot. This imposes two problems:
> 
> 1) a user doesn't see the deprecation warning; and
> 2) with v6.18 kernel, the read-write remount fails because of unknown attr2 option rendering system unusable:

...aaand that's the second failed deprecation in the kernel in the past
month because someone missed a detail somewhere for years and nobody
noticed.

> systemd[1]: Switching root.
> systemd-remount-fs[225]: /usr/bin/mount for / exited with exit status 32.
> 
> # mount -o rw /
> mount: /: fsconfig() failed: xfs: Unknown parameter 'attr2'.
> 
> Thorsten (in Cc) suggested reporting this as a user-visible regression.
> 
> From my PoV, although the deprecation is in place for 5 years already,
> it may not be visible enough as the warning is not emitted for rootfs.
> Considering the amount of systems set up with XFS on /, this may
> impose a mass problem for users.
> 
> Vlastimil suggested making attr2 option a complete noop instead of removing it.
> 
> Please check.

Heh.  Yep, that's a bug.

--D

> Thank you.
> 
> -- 
> Oleksandr Natalenko, MSE



      reply	other threads:[~2025-10-13 21:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-13 19:08 XFS attr2 mount option removal may break system boot Oleksandr Natalenko
2025-10-13 21:29 ` Darrick J. Wong [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=20251013212953.GP6188@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=cem@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=linux@leemhuis.info \
    --cc=oleksandr@natalenko.name \
    --cc=preichl@redhat.com \
    --cc=vbabka@suse.cz \
    /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