summaryrefslogtreecommitdiffstats
path: root/arch/x86/kernel/irq_32.c
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2021-12-12 01:21:06 +0100
committerLinus Torvalds <torvalds@linux-foundation.org>2021-12-12 01:21:06 +0100
commite034d9cbf9f17613c954541f65390be5c35807fc (patch)
tree479d22a987b25b15e01315f4aae2e627d50f6be0 /arch/x86/kernel/irq_32.c
parentMerge branch 'for-5.16-fixes' of git://git.kernel.org/pub/scm/linux/kernel/gi... (diff)
parentxfs: remove all COW fork extents when remounting readonly (diff)
downloadlinux-e034d9cbf9f17613c954541f65390be5c35807fc.tar.xz
linux-e034d9cbf9f17613c954541f65390be5c35807fc.zip
Merge tag 'xfs-5.16-fixes-3' of git://git.kernel.org/pub/scm/fs/xfs/xfs-linux
Pull xfs fix from Darrick Wong: "This fixes a race between a readonly remount process and other processes that hold a file IOLOCK on files that previously experienced copy on write, that could result in severe filesystem corruption if the filesystem is then remounted rw. I think this is fairly rare (since the only reliable reproducer I have that fits the second criteria is the experimental xfs_scrub program), but the race is clear, so we still need to fix this. Summary: - Fix a data corruption vector that can result from the ro remount process failing to clear all speculative preallocations from files and the rw remount process not noticing the incomplete cleanup" * tag 'xfs-5.16-fixes-3' of git://git.kernel.org/pub/scm/fs/xfs/xfs-linux: xfs: remove all COW fork extents when remounting readonly
Diffstat (limited to 'arch/x86/kernel/irq_32.c')
0 files changed, 0 insertions, 0 deletions