xfs: allow inode inactivation during a ro mount log recovery
authorDarrick J. Wong <djwong@kernel.org>
Mon, 11 Sep 2023 15:42:34 +0000 (08:42 -0700)
committerDarrick J. Wong <djwong@kernel.org>
Tue, 12 Sep 2023 17:31:07 +0000 (10:31 -0700)
commit76e589013fec672c3587d6314f2d1f0aeddc26d9
tree4eedead794a5948310d0d8275dbee781f2da6230
parentef7d9593390a050c50eba5fc02d2cb65a1104434
xfs: allow inode inactivation during a ro mount log recovery

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>
Reviewed-by: Dave Chinner <dchinner@redhat.com>
fs/xfs/xfs_inode.c