From: Dave Chinner <david@fromorbit.com>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: chandan.babu@gmail.com, linux-xfs@vger.kernel.org, sandeen@sandeen.net
Subject: Re: [PATCH 1/2] xfs: allow inode inactivation during a ro mount log recovery
Date: Wed, 30 Aug 2023 10:32:17 +1000 [thread overview]
Message-ID: <ZO6OEckBfMWCxcxW@dread.disaster.area> (raw)
In-Reply-To: <169335056933.3525521.6054773682023937525.stgit@frogsfrogsfrogs>
On Tue, Aug 29, 2023 at 04:09:29PM -0700, Darrick J. Wong wrote:
> From: Darrick J. Wong <djwong@kernel.org>
>
> In the next patch, we're going to prohibit log recovery if the primary
> superblock contains an unrecognized rocompat feature bit even on
> readonly mounts. This requires removing all the code in the log
> mounting process that temporarily disables the readonly state.
>
> Unfortunately, inode inactivation disables itself on readonly mounts.
> Clearing the iunlinked lists after log recovery needs inactivation to
> run to free the unreferenced inodes, which (AFAICT) is the only reason
> why log mounting plays games with the readonly state in the first place.
>
> Therefore, change the inactivation predicates to allow inactivation
> during log recovery of a readonly mount.
>
> Signed-off-by: Darrick J. Wong <djwong@kernel.org>
> ---
> fs/xfs/xfs_inode.c | 14 ++++++++++----
> 1 file changed, 10 insertions(+), 4 deletions(-)
Looks good.
Reviewed-by: Dave Chinner <dchinner@redhat.com>
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2023-08-30 1:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-29 23:09 [PATCHSET v2 0/2] xfs: fix ro mounting with unknown rocompat features Darrick J. Wong
2023-08-29 23:09 ` [PATCH 1/2] xfs: allow inode inactivation during a ro mount log recovery Darrick J. Wong
2023-08-30 0:32 ` Dave Chinner [this message]
2023-08-29 23:09 ` [PATCH 2/2] xfs: fix log recovery when unknown rocompat bits are set Darrick J. Wong
2023-08-30 0:31 ` Dave Chinner
2023-08-30 15:23 ` 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=ZO6OEckBfMWCxcxW@dread.disaster.area \
--to=david@fromorbit.com \
--cc=chandan.babu@gmail.com \
--cc=djwong@kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@sandeen.net \
/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