From: Karel Zak <kzak@redhat.com>
To: Stanislav Brabec <sbrabec@suse.cz>
Cc: util-linux@vger.kernel.org
Subject: Re: [PATCH] fsck: implement fsck -r {fd}
Date: Tue, 28 Apr 2015 13:52:10 +0200 [thread overview]
Message-ID: <20150428115210.GW27969@ws.net.home> (raw)
In-Reply-To: <553E53D7.8020800@suse.cz>
Applied, thanks. See notes below.
On Mon, Apr 27, 2015 at 05:20:55PM +0200, Stanislav Brabec wrote:
> Note: Code in if and else is intentionally partially duplicated. Current
> human readable output of floats does not conform to locale conventions,
> and may be changed in future. But we want to keep machine readable output
> exactly same as it is now.
The question is if we can change the human readable output. It was
requested by Google and I guess they parse the output.
> +static int report_stats_fd;
> +static FILE *report_stats_file;
It seems that report_stats_fd does not have to be global variable,
code depends on report_stats_file. Fixed.
> case 'r':
> report_stats = 1;
> + if (arg[j+1]) { /* -r<fd> */
> + report_stats_fd = string_to_int(arg+j+1);
> + if (report_stats_fd < 0)
> + report_stats_fd = 0;
> + else
> + goto next_arg;
> + } else if (i+1 < argc && *argv[i+1] != '-') { /* -r <fd> */
> + report_stats_fd = string_to_int(argv[i+1]);
> + if (report_stats_fd < 0)
> + report_stats_fd = 0;
> + else {
> + ++i;
> + goto next_arg;
> + }
> + }
> break;
...you have copied code from -C, right?
The -C code interprets errors or missing fd as 0, it's probably
because fsck.extN requires file descriptor for -C, but fsck(8) has the
fd as optional argument.
I don't think we need this behavior for -r too. It would be better to
report all possible mistakes. Fixed.
> + /* Validate the report stats file descriptor to avoid disasters */
> + if (report_stats_fd) {
> + report_stats_file = fdopen(report_stats_fd, "w");
> + if (!report_stats_file)
> + err(FSCK_EX_ERROR,
> + _("invalid argument -r %d"),
> + report_stats_fd);
> + }
> +
It means that "-r 0" is unsupported, why? I have fixed this.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2015-04-28 11:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-27 15:20 [PATCH] fsck: implement fsck -r {fd} Stanislav Brabec
2015-04-28 11:52 ` Karel Zak [this message]
2015-04-28 14:15 ` Theodore Ts'o
2015-04-28 15:56 ` Stanislav Brabec
2015-04-28 17:13 ` Theodore Ts'o
2015-04-28 18:30 ` Stanislav Brabec
2015-04-28 15:28 ` Stanislav Brabec
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=20150428115210.GW27969@ws.net.home \
--to=kzak@redhat.com \
--cc=sbrabec@suse.cz \
--cc=util-linux@vger.kernel.org \
/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