diff options
| author | Darrick J. Wong <djwong@kernel.org> | 2021-03-02 20:32:53 +0300 |
|---|---|---|
| committer | Darrick J. Wong <djwong@kernel.org> | 2021-03-15 18:50:40 +0300 |
| commit | d336f7ebc65007f5831e2297e6f3383ae8dbf8ed (patch) | |
| tree | 158d5f81cfb6ae6619115c1907240ec909093a95 /Documentation | |
| parent | b5a08423da9da59c7f38ed8dbb6dd6cbbe9024a4 (diff) | |
| download | linux-d336f7ebc65007f5831e2297e6f3383ae8dbf8ed.tar.xz | |
xfs: force log and push AIL to clear pinned inodes when aborting mount
If we allocate quota inodes in the process of mounting a filesystem but
then decide to abort the mount, it's possible that the quota inodes are
sitting around pinned by the log. Now that inode reclaim relies on the
AIL to flush inodes, we have to force the log and push the AIL in
between releasing the quota inodes and kicking off reclaim to tear down
all the incore inodes. Do this by extracting the bits we need from the
unmount path and reusing them. As an added bonus, failed writes during
a failed mount will not retry forever now.
This was originally found during a fuzz test of metadata directories
(xfs/1546), but the actual symptom was that reclaim hung up on the quota
inodes.
Signed-off-by: Darrick J. Wong <djwong@kernel.org>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Dave Chinner <dchinner@redhat.com>
Diffstat (limited to 'Documentation')
0 files changed, 0 insertions, 0 deletions