From: Zheng Liu <gnehzuil.liu@gmail.com>
To: Robert Yang <liezhi.yang@windriver.com>
Cc: tytso@mit.edu, linux-ext4@vger.kernel.org
Subject: Re: [PATCH] e2fsprogs: misc/mke2fs.c: return error when failed to populate fs
Date: Sat, 22 Mar 2014 12:11:21 +0800 [thread overview]
Message-ID: <20140322041121.GA22353@gmail.com> (raw)
In-Reply-To: <1395295766-10637-1-git-send-email-liezhi.yang@windriver.com>
On Thu, Mar 20, 2014 at 02:09:26PM +0800, Robert Yang wrote:
> We need return retval when "mke2fs -d" failed, otherwise the "$?" would
> be 0 which is misleading.
>
> Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
> ---
> misc/mke2fs.c | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/misc/mke2fs.c b/misc/mke2fs.c
> index aecd5d5..f659e6f 100644
> --- a/misc/mke2fs.c
> +++ b/misc/mke2fs.c
> @@ -2990,10 +2990,11 @@ no_journal:
>
> retval = populate_fs(fs, EXT2_ROOT_INO, root_dir,
> EXT2_ROOT_INO);
> - if (retval)
> + if (retval) {
> fprintf(stderr, "%s",
> - _("\nError while populating file system"));
^^^
Using com_err() is sane. After we get an error, the user can know which
error has occured.
> - else if (!quiet)
> + _("\nError while populating file system\n"));
> + return retval;
^^^^
Maybe exit(1) is better. We just need to notify the user that an error
has occured. An internal error of libext2fs should not be returned
to user.
Regards,
- Zheng
> + } else if (!quiet)
> printf("%s", _("done\n"));
> }
>
> --
> 1.8.3.1
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-03-22 4:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-20 6:09 [PATCH] e2fsprogs: misc/mke2fs.c: return error when failed to populate fs Robert Yang
2014-03-22 4:11 ` Zheng Liu [this message]
2014-03-27 1:55 ` Robert Yang
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=20140322041121.GA22353@gmail.com \
--to=gnehzuil.liu@gmail.com \
--cc=liezhi.yang@windriver.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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.