aboutsummaryrefslogtreecommitdiffstats
path: root/arch/blackfin
diff options
context:
space:
mode:
authorFilipe Manana <fdmanana@suse.com>2020-03-10 12:13:53 +0000
committerDavid Sterba <dsterba@suse.com>2020-03-13 22:15:09 +0100
commit236ebc20d9afc5e9ff52f3cf3f365a91583aac10 (patch)
tree6a8a5cf16f009e8a9e6dd24cefb43cff9a5f0d21 /arch/blackfin
parentbtrfs: fix RAID direct I/O reads with alternate csums (diff)
downloadlinux-dev-236ebc20d9afc5e9ff52f3cf3f365a91583aac10.tar.xz
linux-dev-236ebc20d9afc5e9ff52f3cf3f365a91583aac10.zip
btrfs: fix log context list corruption after rename whiteout error
During a rename whiteout, if btrfs_whiteout_for_rename() returns an error we can end up returning from btrfs_rename() with the log context object still in the root's log context list - this happens if 'sync_log' was set to true before we called btrfs_whiteout_for_rename() and it is dangerous because we end up with a corrupt linked list (root->log_ctxs) as the log context object was allocated on the stack. After btrfs_rename() returns, any task that is running btrfs_sync_log() concurrently can end up crashing because that linked list is traversed by btrfs_sync_log() (through btrfs_remove_all_log_ctxs()). That results in the same issue that commit e6c617102c7e4 ("Btrfs: fix log context list corruption after rename exchange operation") fixed. Fixes: d4682ba03ef618 ("Btrfs: sync log after logging new name") CC: stable@vger.kernel.org # 4.19+ Signed-off-by: Filipe Manana <fdmanana@suse.com> Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'arch/blackfin')
0 files changed, 0 insertions, 0 deletions