summaryrefslogtreecommitdiff
path: root/arch/blackfin/kernel/gptimers.c
diff options
context:
space:
mode:
authorDarrick J. Wong <djwong@kernel.org>2021-06-18 08:54:36 -0700
committerDarrick J. Wong <djwong@kernel.org>2021-06-18 11:51:40 -0700
commit386a03c009b9571cbbad9554c6f55d2450ac7f25 (patch)
tree41385d04ef86ebe9b5b362a37dc845b230c85733 /arch/blackfin/kernel/gptimers.c
parentd3c6e43f9de759907e37fca2be74196281798294 (diff)
xfs: force the log offline when log intent item recovery failslog-recovery-fixes-5.14_2021-06-18
If any part of log intent item recovery fails, we should shut down the log immediately to stop the log from writing a clean unmount record to disk, because the metadata is not consistent. The inability to cancel a dirty transaction catches most of these cases, but there are a few things that have slipped through the cracks, such as ENOSPC from a transaction allocation, or runtime errors that result in cancellation of a non-dirty transaction. This solves some weird behaviors reported by customers where a system goes down, the first mount fails, the second succeeds, but then the fs goes down later because of inconsistent metadata. Signed-off-by: Darrick J. Wong <djwong@kernel.org> Reviewed-by: Christoph Hellwig <hch@lst.de>
Diffstat (limited to 'arch/blackfin/kernel/gptimers.c')
0 files changed, 0 insertions, 0 deletions