linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Laight <David.Laight@ACULAB.COM>
To: 'Masahiro Yamada' <masahiroy@kernel.org>,
	Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>
Cc: Ryan Cai <ycaibb@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] kconfig: fix missing fclose() on error paths
Date: Fri, 11 Feb 2022 11:46:59 +0000	[thread overview]
Message-ID: <37efb2079f5443feaf4f0b10e15a57db@AcuMS.aculab.com> (raw)
In-Reply-To: <CAK7LNASojfnOaAmgwwCsA9J-nhYtRzJx8AKmy8OpRm50uWfegQ@mail.gmail.com>

From: Masahiro Yamada
> Sent: 10 February 2022 00:54
> >
> > The file is not closed when ferror() fails.
> >
> > Fixes: 00d674cb3536 ("kconfig: refactor conf_write_dep()")
> > Fixes: 57ddd07c4560 ("kconfig: refactor conf_write_autoconf()")
> > Reported-by: Ryan Cai <ycaibb@gmail.com>
> > Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
> > ---
> 
> 
> Applied to linux-kbuild/fixes.
> 
> 
> >
> >  scripts/kconfig/confdata.c | 12 ++++++------
> >  1 file changed, 6 insertions(+), 6 deletions(-)
> >
> > diff --git a/scripts/kconfig/confdata.c b/scripts/kconfig/confdata.c
> > index 59717be31210..16897cb8cefd 100644
> > --- a/scripts/kconfig/confdata.c
> > +++ b/scripts/kconfig/confdata.c
> > @@ -979,10 +979,10 @@ static int conf_write_autoconf_cmd(const char *autoconf_name)
> >
> >         fprintf(out, "\n$(deps_config): ;\n");
> >
> > -       if (ferror(out)) /* error check for all fprintf() calls */
> > -               return -1;
> > -
> > +       ret = ferror(out); /* error check for all fprintf() calls */
> >         fclose(out);
> > +       if (ret)
> > +               return -1;

There's not much point calling ferror() unless you call fflush() first.

Similarly there's about zero point in checking the return from fprintf().
At least I've never found any distro adding 'must_check' to fprintf().
('must_not_check' would be more appropriate!)

	David

-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)

  reply	other threads:[~2022-02-11 11:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-08  6:26 [PATCH] kconfig: fix missing fclose() on error paths Masahiro Yamada
2022-02-10  0:53 ` Masahiro Yamada
2022-02-11 11:46   ` David Laight [this message]
2022-02-12 16:09     ` 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=37efb2079f5443feaf4f0b10e15a57db@AcuMS.aculab.com \
    --to=david.laight@aculab.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=ycaibb@gmail.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;
as well as URLs for NNTP newsgroup(s).