From: Carlos O'Donell <carlos@redhat.com>
To: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>,
Xi Ruoyao <xry111@xry111.site>,
libc-alpha@sourceware.org
Subject: Re: Ping: [PATCH] libio: Add __nonnull for FILE * arguments of fclose and freopen
Date: Mon, 22 May 2023 08:36:52 -0400 [thread overview]
Message-ID: <8bd8f5a0-b94a-9199-61e8-06fc5b87d79e@redhat.com> (raw)
In-Reply-To: <c3aa3fb8-e5a5-b087-06b6-44fbb2f4daf0@linaro.org>
On 5/16/23 06:04, Adhemerval Zanella Netto wrote:
> Done.
Thanks for pushing this last week!
> On 15/05/23 23:50, Xi Ruoyao wrote:
>> Ping, as this seems reviewed as OK but fallen through two review
>> meetings.
>>
>> On Fri, 2023-04-21 at 14:21 +0800, Xi Ruoyao wrote:
>>> Calling fclose or freopen with a null FILE * is undefined behavior,
>>> and
>>> doing so in practice will cause a SIGSEGV. So it seems suitable for
>>> __nonnull.
>>>
>>> This will help the compiler to warn for some buggy code, like
>>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109570.
>>> ---
>>> libio/stdio.h | 6 +++---
>>> 1 file changed, 3 insertions(+), 3 deletions(-)
>>>
>>> diff --git a/libio/stdio.h b/libio/stdio.h
>>> index 45ddafdf20..bfb8415d3b 100644
>>> --- a/libio/stdio.h
>>> +++ b/libio/stdio.h
>>> @@ -180,7 +180,7 @@ extern int renameat2 (int __oldfd, const char
>>> *__old, int __newfd,
>>>
>>> This function is a possible cancellation point and therefore not
>>> marked with __THROW. */
>>> -extern int fclose (FILE *__stream);
>>> +extern int fclose (FILE *__stream) __nonnull ((1));
>>>
>>> #undef __attr_dealloc_fclose
>>> #define __attr_dealloc_fclose __attr_dealloc (fclose, 1)
>>> @@ -269,7 +269,7 @@ extern FILE *fopen (const char *__restrict
>>> __filename,
>>> marked with __THROW. */
>>> extern FILE *freopen (const char *__restrict __filename,
>>> const char *__restrict __modes,
>>> - FILE *__restrict __stream) __wur;
>>> + FILE *__restrict __stream) __wur __nonnull
>>> ((3));
>>> #else
>>> # ifdef __REDIRECT
>>> extern FILE *__REDIRECT (fopen, (const char *__restrict __filename,
>>> @@ -290,7 +290,7 @@ extern FILE *fopen64 (const char *__restrict
>>> __filename,
>>> __attribute_malloc__ __attr_dealloc_fclose __wur;
>>> extern FILE *freopen64 (const char *__restrict __filename,
>>> const char *__restrict __modes,
>>> - FILE *__restrict __stream) __wur;
>>> + FILE *__restrict __stream) __wur __nonnull
>>> ((3));
>>> #endif
>>>
>>> #ifdef __USE_POSIX
>>
>
--
Cheers,
Carlos.
prev parent reply other threads:[~2023-05-22 12:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-21 6:21 Xi Ruoyao
2023-04-21 13:00 ` Adhemerval Zanella Netto
2023-04-22 7:32 ` Xi Ruoyao
2023-05-16 2:50 ` Ping: " Xi Ruoyao
2023-05-16 10:04 ` Adhemerval Zanella Netto
2023-05-22 12:36 ` Carlos O'Donell [this message]
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=8bd8f5a0-b94a-9199-61e8-06fc5b87d79e@redhat.com \
--to=carlos@redhat.com \
--cc=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.org \
--cc=xry111@xry111.site \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).