public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org, Filipe Manana <fdmanana@suse.com>
Subject: Re: [PATCH] btrfs: scrub: Require mandatory block group RO for dev-replace
Date: Thu, 23 Jan 2020 17:40:43 +0100	[thread overview]
Message-ID: <20200123164043.GE3929@twin.jikos.cz> (raw)
In-Reply-To: <20200123073759.23535-1-wqu@suse.com>

On Thu, Jan 23, 2020 at 03:37:59PM +0800, Qu Wenruo wrote:
> 
> Reported-by: Filipe Manana <fdmanana@suse.com>
> Fixes: 76a8efa171bf ("btrfs: Continue replace when set_block_ro failed")
> Fixes: b12de52896c0 ("btrfs: scrub: Don't check free space before marking a block group RO")

This one is in the 5.5-rc, so I'd like to get it to the final release. I
haven't read the discussion properly so please let me know if the patch
needs another round or fixups I can do. Time for the pull request is in
a day (2 at most as it's too close to the release) but given the type of
fix it's justified. Thanks.

  parent reply	other threads:[~2020-01-23 16:41 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-23  7:37 [PATCH] btrfs: scrub: Require mandatory block group RO for dev-replace Qu Wenruo
2020-01-23 12:06 ` Filipe Manana
2020-01-23 12:28   ` Qu WenRuo
2020-01-23 13:39   ` Qu Wenruo
2020-01-23 13:49     ` Filipe Manana
2020-01-23 13:57       ` Qu Wenruo
2020-01-23 16:40 ` David Sterba [this message]
2020-01-23 23:58   ` Qu Wenruo
  -- strict thread matches above, loose matches on Subject: below --
2020-01-23 23:58 Qu Wenruo
2020-01-24  9:24 ` Filipe Manana
2020-01-24 13:40   ` David Sterba
2020-01-24 14:44 ` David Sterba
2020-01-24 16:28   ` Filipe Manana
2020-01-25  0:36     ` Qu Wenruo
2020-01-25  0:48       ` Qu Wenruo
2020-01-25 11:35       ` David Sterba
2020-01-25 12:09         ` Qu WenRuo

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=20200123164043.GE3929@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=fdmanana@suse.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=wqu@suse.com \
    /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