From: Dave Chinner <david@fromorbit.com>
To: jeffm@suse.com
Cc: linux-xfs@vger.kernel.org, Eric Sandeen <sandeen@sandeen.net>
Subject: Re: [PATCH] mkfs: fix divide-by-zero in align_ag_geometry
Date: Thu, 21 Jun 2018 13:57:49 +1000 [thread overview]
Message-ID: <20180621035749.GR19934@dastard> (raw)
In-Reply-To: <20180621025520.9115-1-jeffm@suse.com>
On Wed, Jun 20, 2018 at 10:55:20PM -0400, jeffm@suse.com wrote:
> From: Jeff Mahoney <jeffm@suse.com>
>
> Commit 051b4e37f5e (mkfs: factor AG alignment) factored out the
> AG alignment code into a separate function. It got rid of
> redundant checks for dswidth != 0 but did too good a job since now
> it doesn't check at all.
Of course they got removed - we've already validated the CLI input
and guaranteed that cfg->dswidth can only be zero iff cfg->dsunit is
zero in calc_stripe_factors().
i.e. We do input validation of CLI paramters before anything else so
that later users (like align_ag_geometry()) can assume the
parameters they are using are valid. In this case, the assumption is
that either both dsunit and dswidth are zero or that both are
non-zero and dswidth an integer multple of dsunit.
> When we hit the check to see if agsize
> is a multiple of stripe width: (cfg->agsize % cfg->dswidth), we crash
> on a divide by zero.
What CLI config did you use to hit this? I'd like to reproduce it so
I can see where calc_stripe_factors() is going wrong....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2018-06-21 3:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-21 2:55 [PATCH] mkfs: fix divide-by-zero in align_ag_geometry jeffm
2018-06-21 3:57 ` Dave Chinner [this message]
2018-06-21 19:15 ` Jeff Mahoney
2018-06-21 19:26 ` Eric Sandeen
2018-06-21 19:49 ` Dave Chinner
2018-06-21 21:31 ` Jeff Mahoney
2018-06-21 22:36 ` Dave Chinner
2018-06-21 23:16 ` Eric Sandeen
2018-06-22 1:34 ` Eric Sandeen
2018-06-22 1:40 ` Jeff Mahoney
2018-07-19 21:09 ` Jeff Mahoney
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=20180621035749.GR19934@dastard \
--to=david@fromorbit.com \
--cc=jeffm@suse.com \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@sandeen.net \
/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