Re: FAILED: patch "[PATCH] btrfs: handle logged extent failure properly" failed to apply to 5.6-stable tree

[Sasha Levin <sashal@kernel.org>]

On Tue, Apr 14, 2020 at 04:21:45PM +0200, gregkh@linuxfoundation.org wrote:
>
>The patch below does not apply to the 5.6-stable tree.
>If someone wants it applied there, or to any other stable or longterm
>tree, then please email the backport, including the original git commit
>id to <stable@vger.kernel.org>.
>
>thanks,
>
>greg k-h
>
>------------------ original commit in Linus's tree ------------------
>
>From ab9b2c7b32e6be53cac2e23f5b2db66815a7d972 Mon Sep 17 00:00:00 2001
>From: Josef Bacik <josef@toxicpanda.com>
>Date: Thu, 13 Feb 2020 10:47:30 -0500
>Subject: [PATCH] btrfs: handle logged extent failure properly
>
>If we're allocating a logged extent we attempt to insert an extent
>record for the file extent directly.  We increase
>space_info->bytes_reserved, because the extent entry addition will call
>btrfs_update_block_group(), which will convert the ->bytes_reserved to
>->bytes_used.  However if we fail at any point while inserting the
>extent entry we will bail and leave space on ->bytes_reserved, which
>will trigger a WARN_ON() on umount.  Fix this by pinning the space if we
>fail to insert, which is what happens in every other failure case that
>involves adding the extent entry.
>
>CC: stable@vger.kernel.org # 5.4+
>Reviewed-by: Johannes Thumshirn <johannes.thumshirn@wdc.com>
>Reviewed-by: Nikolay Borisov <nborisov@suse.com>
>Reviewed-by: Qu Wenruo <wqu@suse.com>
>Signed-off-by: Josef Bacik <josef@toxicpanda.com>
>Reviewed-by: David Sterba <dsterba@suse.com>
>Signed-off-by: David Sterba <dsterba@suse.com>

Greg, I've noticed that you've fixed it up for 5.5 and 5.4 but no for
5.6? I've queued it up for 5.6 as well.

-- 
Thanks,
Sasha