diff options
| author | Eric Sandeen <sandeen@sandeen.net> | 2017-09-17 21:06:47 (GMT) |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2017-09-20 06:19:59 (GMT) |
| commit | 9a3f752290907e7bfa80a333e4965574932f5670 (patch) | |
| tree | 401c14bf875e82581c85700ac78ab9fd75a4a818 /fs/xfs/xfs_aops.c | |
| parent | 01d38e380746e5880d744c634f0c459ea6646dd9 (diff) | |
| download | linux-9a3f752290907e7bfa80a333e4965574932f5670.tar.xz | |
xfs: toggle readonly state around xfs_log_mount_finish
commit 6f4a1eefdd0ad4561543270a7fceadabcca075dd upstream.
When we do log recovery on a readonly mount, unlinked inode
processing does not happen due to the readonly checks in
xfs_inactive(), which are trying to prevent any I/O on a
readonly mount.
This is misguided - we do I/O on readonly mounts all the time,
for consistency; for example, log recovery. So do the same
RDONLY flag twiddling around xfs_log_mount_finish() as we
do around xfs_log_mount(), for the same reason.
This all cries out for a big rework but for now this is a
simple fix to an obvious problem.
Signed-off-by: Eric Sandeen <sandeen@redhat.com>
Reviewed-by: Brian Foster <bfoster@redhat.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com>
Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'fs/xfs/xfs_aops.c')
0 files changed, 0 insertions, 0 deletions