From: Tom Rini <trini@konsulko.com>
To: linux-kbuild@vger.kernel.org
Cc: Michal Marek <mmarek@suse.com>, lk <linux-kernel@vger.kernel.org>,
stable@vger.kernel.org
Subject: Re: [PATCH] kbuild: fixdep: Check fstat(2) return value
Date: Sat, 16 Jan 2016 14:14:27 -0500 [thread overview]
Message-ID: <20160116191427.GU3359@bill-the-cat> (raw)
In-Reply-To: <1449523568-31084-1-git-send-email-trini@konsulko.com>
On Mon, Dec 7, 2015 at 4:26 PM, Tom Rini <trini@konsulko.com> wrote:
> Coverity has recently added a check that will find when we don't check
> the return code from fstat(2). Copy/paste the checking logic that
> print_deps() has with an appropriate re-wording of the perror() message.
>
> Cc: Michal Marek <mmarek@suse.com>
> Cc: linux-kbuild@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org
> Signed-off-by: Tom Rini <trini@konsulko.com>
>
> ---
> Note that I don't have a CID here was I found this in U-Boot and the
> kernel hasn't yet done a build with this test being enabled.
> ---
> scripts/basic/fixdep.c | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/scripts/basic/fixdep.c b/scripts/basic/fixdep.c
> index c68fd61..e3d9678 100644
> --- a/scripts/basic/fixdep.c
> +++ b/scripts/basic/fixdep.c
> @@ -274,7 +274,11 @@ static void do_config_file(const char *filename)
> perror(filename);
> exit(2);
> }
> - fstat(fd, &st);
> + if (fstat(fd, &st) < 0) {
> + fprintf(stderr, "fixdep: error fstat'ing config file: ");
> + perror(filename);
> + exit(2);
> + }
> if (st.st_size == 0) {
> close(fd);
> return;
Adding stable@ since this applies to 4.4. Any comments? Thanks!
--
Tom
next prev parent reply other threads:[~2016-01-16 19:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-07 21:26 [PATCH] kbuild: fixdep: Check fstat(2) return value Tom Rini
2016-01-16 19:14 ` Tom Rini [this message]
[not found] ` <CA+M6bXnTB286iFoSFUneGq=1PCJtmnR_PBrqMeM4eu-Aj1BqMA@mail.gmail.com>
2016-02-16 15:32 ` Tom Rini
2016-02-17 21:58 ` Michal Marek
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=20160116191427.GU3359@bill-the-cat \
--to=trini@konsulko.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.com \
--cc=stable@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