Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: gregkh@linuxfoundation.org
Cc: josef@toxicpanda.com, dsterba@suse.com, nborisov@suse.com,
	stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] btrfs: use btrfs_block_group_cache_done in update_block_group" failed to apply to 5.3-stable tree
Date: Sun, 15 Dec 2019 13:45:30 -0500	[thread overview]
Message-ID: <20191215184530.GO18043@sasha-vm> (raw)
In-Reply-To: <1576408118186153@kroah.com>

On Sun, Dec 15, 2019 at 12:08:38PM +0100, gregkh@linuxfoundation.org wrote:
>
>The patch below does not apply to the 5.3-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 a60adce85f4bb5c1ef8ffcebadd702cafa2f3696 Mon Sep 17 00:00:00 2001
>From: Josef Bacik <josef@toxicpanda.com>
>Date: Tue, 24 Sep 2019 16:50:44 -0400
>Subject: [PATCH] btrfs: use btrfs_block_group_cache_done in update_block_group
>
>When free'ing extents in a block group we check to see if the block
>group is not cached, and then cache it if we need to.  However we'll
>just carry on as long as we're loading the cache.  This is problematic
>because we are dirtying the block group here.  If we are fast enough we
>could do a transaction commit and clear the free space cache while we're
>still loading the space cache in another thread.  This truncates the
>free space inode, which will keep it from loading the space cache.
>
>Fix this by using the btrfs_block_group_cache_done helper so that we try
>to load the space cache unconditionally here, which will result in the
>caller waiting for the fast caching to complete and keep us from
>truncating the free space inode.
>
>CC: stable@vger.kernel.org # 4.4+
>Signed-off-by: Josef Bacik <josef@toxicpanda.com>
>Reviewed-by: Nikolay Borisov <nborisov@suse.com>
>Signed-off-by: David Sterba <dsterba@suse.com>

The code just moved around a lot. I've fixed it up and queued for all
branches.

-- 
Thanks,
Sasha

      reply	other threads:[~2019-12-15 18:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-15 11:08 FAILED: patch "[PATCH] btrfs: use btrfs_block_group_cache_done in update_block_group" failed to apply to 5.3-stable tree gregkh
2019-12-15 18:45 ` Sasha Levin [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191215184530.GO18043@sasha-vm \
    --to=sashal@kernel.org \
    --cc=dsterba@suse.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=josef@toxicpanda.com \
    --cc=nborisov@suse.com \
    --cc=stable@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox