All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Jarosch <thomas.jarosch-XXsH3GEs1jrby3iVrkZq2A@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [man-pages PATCH] Add note about calling fclose(NULL)
Date: Tue, 29 Jan 2013 17:24:43 +0100	[thread overview]
Message-ID: <1695270.M7m4ekngnN@storm> (raw)


Signed-off-by: Thomas Jarosch <thomas.jarosch-XXsH3GEs1jrby3iVrkZq2A@public.gmane.org>
---
 man3/fclose.3 | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/man3/fclose.3 b/man3/fclose.3
index 1bdf0a5..6945e89 100644
--- a/man3/fclose.3
+++ b/man3/fclose.3
@@ -97,6 +97,10 @@ on disk the kernel buffers must be flushed too, for example, with
 .BR sync (2)
 or
 .BR fsync (2).
+Also it's undefined behavior to call
+.BR fclose ()
+with a NULL pointer.
+
 .SH "SEE ALSO"
 .BR close (2),
 .BR fcloseall (3),
-- 
1.7.11.7

--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2013-01-29 16:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-29 16:24 Thomas Jarosch [this message]
2013-01-29 18:44 ` [man-pages PATCH] Add note about calling fclose(NULL) Mike Frysinger
     [not found]   ` <201301291344.29011.vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
2013-02-01  9:43     ` Thomas Jarosch
2013-02-02  9:35       ` Mike Frysinger
2013-01-31  0:50 ` Michael Kerrisk (man-pages)
     [not found]   ` <CAKgNAkiQsWWWTfLWeixN5+GcwkfP6UX+AYdL4HY6beq7rdpUxw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-01-31  8:26     ` Thomas Jarosch
2013-02-02  1:11       ` Michael Kerrisk

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=1695270.M7m4ekngnN@storm \
    --to=thomas.jarosch-xxsh3ges1jrby3ivrkzq2a@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.