From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2] btrfs: scrub: Don't check free space before marking a block group RO
Date: Mon, 18 Nov 2019 16:14:25 +0100 [thread overview]
Message-ID: <20191118151425.GF3001@twin.jikos.cz> (raw)
In-Reply-To: <20191115020900.23662-1-wqu@suse.com>
On Fri, Nov 15, 2019 at 10:09:00AM +0800, Qu Wenruo wrote:
...
> Signed-off-by: Qu Wenruo <wqu@suse.com>
>
> ---
> This version is based on v5.4-rc1, for a commonly known commit hash.
> It would cause conflicts due to
> btrfs_block_group_cache -> btrfs_block_group refactor.
>
> The conflicts should be easy to solve.
>
> Changelog:
> v2:
> - Fix a bug that previous verion never do chunk pre-allocation.
> - Avoid chunk pre-allocation from check_system_chunk()
> - Use extra parameter @do_chunk_alloc other than new function with
> "_force" suffix.
> - Skip unnecessary update_block_group_flags() call completely for
> do_chunk_alloc=false case.
Added to misc-next, thanks.
next prev parent reply other threads:[~2019-11-18 15:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-15 2:09 [PATCH v2] btrfs: scrub: Don't check free space before marking a block group RO Qu Wenruo
2019-11-15 12:51 ` Filipe Manana
2019-11-18 15:14 ` David Sterba [this message]
2020-01-17 17:59 ` Filipe Manana
2020-01-18 1:16 ` Qu Wenruo
2020-01-20 9:43 ` Qu Wenruo
2020-01-20 10:45 ` Filipe Manana
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=20191118151425.GF3001@twin.jikos.cz \
--to=dsterba@suse.cz \
--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;
as well as URLs for NNTP newsgroup(s).