summaryrefslogtreecommitdiff
path: root/.gitignore
diff options
context:
space:
mode:
authorDarrick J. Wong <djwong@kernel.org>2021-03-22 09:51:51 -0700
committerDarrick J. Wong <djwong@kernel.org>2021-03-25 16:59:55 -0700
commitde48956f07a3dc992b33fd2794d64142f93e4b9a (patch)
treef90cd43b383e404fd7f18546e9950f4255cf22c5 /.gitignore
parent09ad1f2843dad8283cea79f4f50e22e1007302e9 (diff)
xfs: fix scrub and remount-ro protection when running scrubrandom-fixes-5.13_2021-03-25
While running a new fstest that races a readonly remount with scrub running in repair mode, I observed the kernel tripping over debugging assertions in the log quiesce code that were checking that the CIL was empty. When the sysadmin runs scrub in repair mode, the scrub code allocates real transactions (with reservations) to change things, but doesn't increment the superblock writers count to block a readonly remount attempt while it is running. We don't require the userspace caller to have a writable file descriptor to run repairs, so we have to call mnt_want_write_file to obtain freeze protection and increment the writers count. It's ok to remove the call to sb_start_write for the dry-run case because commit 8321ddb2fa29 removed the behavior where scrub and fsfreeze fight over the buffer LRU. Signed-off-by: Darrick J. Wong <djwong@kernel.org>
Diffstat (limited to '.gitignore')
0 files changed, 0 insertions, 0 deletions