Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] mke2img: add parameter sanity checks to prevent odd error messages from genext2.fs
Date: Sat, 29 Apr 2017 21:06:06 +0200	[thread overview]
Message-ID: <20170429210606.37872b68@free-electrons.com> (raw)
In-Reply-To: <1493481682-128366-2-git-send-email-g4@novadsp.com>

Hello,

On Sat, 29 Apr 2017 17:01:22 +0100, J Evans wrote:

> +    if [ -z "${nb_blocks}" ]; then
> +        error "Error: you must specify a file system block count with '-b'. This cannot be zero, e.g. 61440 == 60MB\n"
> +    fi

Check this is useless: there is already error checking done by getopt
itself, because the -b option *must* have an argument. Indeed, the
current mke2img behaves like this:

$ ./package/mke2img/mke2img -b
mke2img: option 'b' expects a mandatory argument

So it is already checked that ${nb_blocks} cannot be empty.

> +    if [ "${nb_blocks}" -eq 0 ]; then
> +        error "Error: The file system block count size cannot be zero. e.g. 61440 == 60MB \n"
> +    fi

See my reply to the previous commit: I don't see why 0 should be
checked specifically. Please explain in the commit log why it should be.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2017-04-29 19:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-29 16:01 [Buildroot] [PATCH 1/2] ext2.mk: ensure file system block count is not zero (0) J Evans
2017-04-29 16:01 ` [Buildroot] [PATCH 2/2] mke2img: add parameter sanity checks to prevent odd error messages from genext2.fs J Evans
2017-04-29 19:06   ` Thomas Petazzoni [this message]
2017-04-30  9:25     ` Yann E. MORIN
2017-04-30  9:32       ` Thomas Petazzoni
2017-04-29 19:03 ` [Buildroot] [PATCH 1/2] ext2.mk: ensure file system block count is not zero (0) Thomas Petazzoni
2017-04-30  9:18   ` Yann E. MORIN
2017-04-30 12:18     ` jerry at chordia.co.uk

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=20170429210606.37872b68@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.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