From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Vlastimil Babka <vbabka@suse.cz>,
Carlos Maiolino <cem@kernel.org>,
linux-kernel@vger.kernel.org, linux-xfs@vger.kernel.org,
Oleksandr Natalenko <oleksandr@natalenko.name>,
Pavel Reichl <preichl@redhat.com>,
Thorsten Leemhuis <linux@leemhuis.info>
Subject: Re: [PATCH v2 3/3] xfs: quietly ignore deprecated mount options
Date: Thu, 16 Oct 2025 22:45:28 -0700 [thread overview]
Message-ID: <aPHX-Iq2KOccWw-h@infradead.org> (raw)
In-Reply-To: <20251015153702.GY6188@frogsfrogsfrogs>
On Wed, Oct 15, 2025 at 08:37:02AM -0700, Darrick J. Wong wrote:
> won't have to deal with attr1 structures anymore, because V5 always has
> attr2.
There's isn't really any attr1 structures anyway, it's really just
lex flexible (aka) dump partitioning of the space in the inode.
> I think you're right, we should keep this forever. It's not that big of
> a deal to accumulate all the dead mount options via fsparam_dead, and
> probably a good tombstone to prevent accidental reuse in the future.
Agreed.
next prev parent reply other threads:[~2025-10-17 5:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-15 5:01 [PATCH v2 1/3] xfs: don't set bt_nr_sectors to a negative number Darrick J. Wong
2025-10-15 5:03 ` [PATCH v2 2/3] xfs: always warn about deprecated mount options Darrick J. Wong
2025-10-15 5:04 ` [PATCH v2 3/3] xfs: quietly ignore " Darrick J. Wong
2025-10-15 8:07 ` Vlastimil Babka
2025-10-15 15:37 ` Darrick J. Wong
2025-10-17 5:45 ` Christoph Hellwig [this message]
2025-10-17 5:46 ` Christoph Hellwig
2025-10-16 16:25 ` [PATCH 4/3] xfs: fix locking in xchk_nlinks_collect_dir Darrick J. Wong
2025-10-17 5:48 ` Christoph Hellwig
2025-10-21 17:57 ` Darrick J. Wong
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=aPHX-Iq2KOccWw-h@infradead.org \
--to=hch@infradead.org \
--cc=cem@kernel.org \
--cc=djwong@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