summaryrefslogtreecommitdiff
path: root/arch/x86/kernel/crash_core_64.c
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2021-08-01 12:07:23 -0700
committerLinus Torvalds <torvalds@linux-foundation.org>2021-08-01 12:07:23 -0700
commitaa6603266cc0760ebb83cf11cb5a2b8fca84cd68 (patch)
tree2f93abfdfd51d5a23e437424caaeb9e3a7d6d207 /arch/x86/kernel/crash_core_64.c
parentf3438b4c4e692b49b7dc2bab864d20381024be16 (diff)
parent81a448d7b0668ae39c08e6f34a54cc7eafb844f1 (diff)
Merge tag 'xfs-5.14-fixes-2' of git://git.kernel.org/pub/scm/fs/xfs/xfs-linux
Pull xfs fixes from Darrick Wong: "This contains a bunch of bug fixes in XFS. Dave and I have been busy the last couple of weeks to find and fix as many log recovery bugs as we can find; here are the results so far. Go fstests -g recoveryloop! ;) - Fix a number of coordination bugs relating to cache flushes for metadata writeback, cache flushes for multi-buffer log writes, and FUA writes for single-buffer log writes - Fix a bug with incorrect replay of attr3 blocks - Fix unnecessary stalls when flushing logs to disk - Fix spoofing problems when recovering realtime bitmap blocks" * tag 'xfs-5.14-fixes-2' of git://git.kernel.org/pub/scm/fs/xfs/xfs-linux: xfs: prevent spoofing of rtbitmap blocks when recovering buffers xfs: limit iclog tail updates xfs: need to see iclog flags in tracing xfs: Enforce attr3 buffer recovery order xfs: logging the on disk inode LSN can make it go backwards xfs: avoid unnecessary waits in xfs_log_force_lsn() xfs: log forces imply data device cache flushes xfs: factor out forced iclog flushes xfs: fix ordering violation between cache flushes and tail updates xfs: fold __xlog_state_release_iclog into xlog_state_release_iclog xfs: external logs need to flush data device xfs: flush data dev on external log write
Diffstat (limited to 'arch/x86/kernel/crash_core_64.c')
0 files changed, 0 insertions, 0 deletions