From: David Sterba <dsterba@suse.cz>
To: Daniel Xu <dxu@dxuuu.xyz>
Cc: linux-btrfs@vger.kernel.org, kernel-team@fb.com,
josef@toxicpanda.com, quwenruo.btrfs@gmx.com,
Qu Wenruo <wqu@suse.com>
Subject: Re: [PATCH v2] btrfs: Fix divide by zero
Date: Fri, 16 Oct 2020 16:33:54 +0200 [thread overview]
Message-ID: <20201016143354.GU6756@twin.jikos.cz> (raw)
In-Reply-To: <20201009010910.270794-1-dxu@dxuuu.xyz>
On Thu, Oct 08, 2020 at 06:09:10PM -0700, Daniel Xu wrote:
> If there's no parity and num_stripes < ncopies, an btrfs image can
> trigger a divide by zero in calc_stripe_length().
>
> The image (see link) was generated through fuzzing.
>
> Reviewed-by: Qu Wenruo <wqu@suse.com>
> Link: https://bugzilla.kernel.org/show_bug.cgi?id=209587
For bugzillas please use Bugzilla: tag.
> Signed-off-by: Daniel Xu <dxu@dxuuu.xyz>
Please write more descriptive subjects like
"btrfs: tree-checker: validate number of chunk stripes and parity"
prev parent reply other threads:[~2020-10-16 14:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-09 1:09 [PATCH v2] btrfs: Fix divide by zero Daniel Xu
2020-10-14 20:26 ` Daniel Xu
2020-10-14 20:44 ` Josef Bacik
2020-10-16 14:33 ` 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=20201016143354.GU6756@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=dxu@dxuuu.xyz \
--cc=josef@toxicpanda.com \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
--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