public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bugdal at aerifal dot cx" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/14627] close() should set errno to EINPROGRESS when interrupted by a signal
Date: Fri, 02 Jan 2015 02:31:00 -0000	[thread overview]
Message-ID: <bug-14627-131-2f7ioiSl7M@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14627-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=14627

--- Comment #2 from Rich Felker <bugdal at aerifal dot cx> ---
I tend to agree. EINPROGRESS is not useful to report, since the operation
already succeeded, and it's potentially going to be misinterpreted, so I think
returning success is preferable.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2015-01-02  2:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-26  4:33 [Bug libc/14627] New: " bugdal at aerifal dot cx
2014-06-13 11:27 ` [Bug libc/14627] " fweimer at redhat dot com
2015-01-02  0:41 ` sstewartgallus00 at mylangara dot bc.ca
2015-01-02  2:31 ` bugdal at aerifal dot cx [this message]
2015-03-31 19:01 ` thib at stammed dot net
2021-07-10 22:34 ` jscott at posteo dot net

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=bug-14627-131-2f7ioiSl7M@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).