From: Lukas Bulwahn <lukas.bulwahn@gmail.com>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Nicholas Mc Guire <der.herr@hofr.at>,
sil2review@lists.osadl.org,
Michal Marek <michal.lkml@markovi.net>,
Sam Ravnborg <sam@ravnborg.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] fixdep: exit with error code in error branches of do_config_file()
Date: Mon, 8 Jan 2018 11:17:10 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1801081109210.3323@hsp> (raw)
In-Reply-To: <CAK7LNAROjcbES8-debAnzVz1EV1Ar+RLW8phF5+bQxpHQUODKQ@mail.gmail.com>
On Sun, 31 Dec 2017, Masahiro Yamada wrote:
> 2017-12-22 4:10 GMT+09:00 Lukas Bulwahn <lukas.bulwahn@gmail.com>:
>> diff --git a/scripts/basic/fixdep.c b/scripts/basic/fixdep.c
>> index bbf62cb..4274610 100644
>> --- a/scripts/basic/fixdep.c
>> +++ b/scripts/basic/fixdep.c
>> @@ -284,19 +284,18 @@ static void do_config_file(const char *filename)
>> exit(2);
>> }
>> if (st.st_size == 0) {
>> - close(fd);
>> - return;
>> + fprintf(stderr, "fixdep: error empty file config file: ");
>> + perror(filename);
>> + exit(2);
>> }
>
> No. This is correct as-is.
>
> do_config_file() does not parse .cmd files
> but parse source files (.c .h .S etc.)
>
> Having an empty source file is rare, but possible.
>
>
Now that I looked at the code for creating the v3 patch, I am confused
about the error messages in scripts/basic/fixdep.c, lines 275 - 285, in
do_config_file():
fd = open(filename, O_RDONLY);
if (fd < 0) {
fprintf(stderr, "fixdep: error opening config file: ");
perror(filename);
exit(2);
}
if (fstat(fd, &st) < 0) {
fprintf(stderr, "fixdep: error fstat'ing config file: ");
perror(filename);
exit(2);
}
These error messages suggest that filename (and the file handler fd)
refers to a config file, but you say that filename and fd refer to source
files.
Looking at parse_dep_file() and how it invokes do_config_file(), I think
you are right that it does refer to source files.
If you confirm that this is correct, I would change `config file` to
`source file` in the error messages of do_config_file().
What is best to do here, provide a separate patch or add it to the
existing patch?
Lukas
next prev parent reply other threads:[~2018-01-08 10:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-20 20:27 [PATCH] " Lukas Bulwahn
2017-12-21 15:33 ` Nicholas Mc Guire
2017-12-21 19:10 ` [PATCH v2] " Lukas Bulwahn
2017-12-30 16:51 ` Masahiro Yamada
2017-12-31 15:45 ` Nicholas Mc Guire
2018-01-01 6:41 ` Masahiro Yamada
2018-01-01 9:31 ` Nicholas Mc Guire
2018-01-01 9:55 ` Sam Ravnborg
2018-01-08 10:17 ` Lukas Bulwahn [this message]
2018-01-09 8:39 ` Masahiro Yamada
2018-01-08 10:04 ` [PATCH v3] " Lukas Bulwahn
2018-01-09 8:26 ` Masahiro Yamada
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=alpine.DEB.2.20.1801081109210.3323@hsp \
--to=lukas.bulwahn@gmail.com \
--cc=der.herr@hofr.at \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.lkml@markovi.net \
--cc=sam@ravnborg.org \
--cc=sil2review@lists.osadl.org \
--cc=yamada.masahiro@socionext.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
all inboxes | Powered by JetHome®