From: David Sterba <dsterba@suse.cz>
To: Johannes Thumshirn <jthumshirn@suse.de>
Cc: Hans van Kranenburg <Hans.van.Kranenburg@mendix.com>,
Liu Bo <obuil.liubo@gmail.com>,
Linux BTRFS Mailinglist <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] btrfs: ensure that a DUP block group has exactly two stripes
Date: Fri, 15 Feb 2019 16:20:18 +0100 [thread overview]
Message-ID: <20190215152018.GD9874@suse.cz> (raw)
In-Reply-To: <01219372-4533-fb72-44fd-b2882c0614f6@suse.de>
On Thu, Feb 14, 2019 at 05:21:54PM +0100, Johannes Thumshirn wrote:
> On 13/02/2019 15:32, Hans van Kranenburg wrote:
> [...]
>
> >> +++ b/fs/btrfs/volumes.c
> >> @@ -6794,7 +6794,7 @@ static int btrfs_check_chunk_valid(struct btrfs_fs_info *fs_info,
> >> (type & BTRFS_BLOCK_GROUP_RAID1 && num_stripes < 1) ||
> >> (type & BTRFS_BLOCK_GROUP_RAID5 && num_stripes < 2) ||
> >> (type & BTRFS_BLOCK_GROUP_RAID6 && num_stripes < 3) ||
> >> - (type & BTRFS_BLOCK_GROUP_DUP && num_stripes > 2) ||
> >> + (type & BTRFS_BLOCK_GROUP_DUP && num_stripes != 2) ||
> >> ((type & BTRFS_BLOCK_GROUP_PROFILE_MASK) == 0 &&
> >> num_stripes != 1)) {
> >> btrfs_err(fs_info,
> >>
> >
> > It looks like the RAID1 check has a similar problem. Shouldn't that
> > check also be != 2 ?
>
> So looking at the code again I think num_stripes == 1 for RAID1 will
> result in the same division by 0 in calc_stripe_length().
>
> I'll send a patch for RAID1 as well unless David speaks up and says he
> wants it amended in this one.
If the explanation and cause is the same, it's ok to put it into one
patch I think, but no strong preference here.
prev parent reply other threads:[~2019-02-15 15:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-13 14:26 [PATCH] btrfs: ensure that a DUP block group has exactly two stripes Johannes Thumshirn
2019-02-13 14:27 ` Nikolay Borisov
2019-02-13 14:32 ` Qu Wenruo
2019-02-13 14:32 ` Hans van Kranenburg
2019-02-13 14:37 ` Johannes Thumshirn
2019-02-13 15:02 ` Nikolay Borisov
2019-02-14 17:27 ` Hans van Kranenburg
2019-02-14 16:21 ` Johannes Thumshirn
2019-02-15 15:20 ` David Sterba [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=20190215152018.GD9874@suse.cz \
--to=dsterba@suse.cz \
--cc=Hans.van.Kranenburg@mendix.com \
--cc=jthumshirn@suse.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=obuil.liubo@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.