summaryrefslogtreecommitdiff
path: root/fs/btrfs/ulist.h
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2019-09-13 09:48:47 +0100
committerLinus Torvalds <torvalds@linux-foundation.org>2019-09-13 09:48:47 +0100
commit1b304a1ae45de4df7d773f0a39d1100aabca615b (patch)
treef8727159a28159faaf07df87ec1d0175d6d9582a /fs/btrfs/ulist.h
parent505a8ec7e11ae5236c4a154a1e24ef49a8349600 (diff)
parent18dfa7117a3f379862dcd3f67cadd678013bb9dd (diff)
Merge tag 'for-5.3-rc8-tag' of git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux
Pull btrfs fixes from David Sterba: "Here are two fixes, one of them urgent fixing a bug introduced in 5.2 and reported by many users. It took time to identify the root cause, catching the 5.3 release is higly desired also to push the fix to 5.2 stable tree. The bug is a mess up of return values after adding proper error handling and honestly the kind of bug that can cause sleeping disorders until it's caught. My appologies to everybody who was affected. Summary of what could happen: 1) either a hang when committing a transaction, if this happens there's no risk of corruption, still the hang is very inconvenient and can't be resolved without a reboot 2) writeback for some btree nodes may never be started and we end up committing a transaction without noticing that, this is really serious and that will lead to the "parent transid verify failed" messages" * tag 'for-5.3-rc8-tag' of git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux: Btrfs: fix unwritten extent buffers and hangs on future writeback attempts Btrfs: fix assertion failure during fsync and use of stale transaction
Diffstat (limited to 'fs/btrfs/ulist.h')
0 files changed, 0 insertions, 0 deletions