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 nptl/14484] sem_timedwait always return -1 with errno 110 (ETIMEDOUT).
Date: Tue, 17 Jun 2014 18:56:00 -0000	[thread overview]
Message-ID: <bug-14484-131-Z7bCqy7bvt@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14484-131@http.sourceware.org/bugzilla/>

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

--- Comment #17 from Rich Felker <bugdal at aerifal dot cx> ---
Rereading the comments thread, I finally understand what the reporter's
misunderstanding is. He seems to think ETIMEDOUT is ONLY for the case where the
abstime passed to sem_timedwait is _already_ in the past at the time of the
call, and that something else (EINTR?) should happen if sem_timedwait
successfully begins waiting but then times out. This expectation is simply
wrong. ETIMEDOUT is the correct error for both cases (and of course formally
they are not demonstrably different since it's not observable whether a thread
has actually entered the sem_timedwait or delayed prior to entry to the
function due to scheduling).

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


      parent reply	other threads:[~2014-06-17 18:56 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-17  5:20 [Bug nptl/14484] New: " tingw.liu at gmail dot com
2012-08-17  6:08 ` [Bug nptl/14484] " bugdal at aerifal dot cx
2012-08-17  6:21 ` tingw.liu at gmail dot com
2012-08-17  6:26 ` tingw.liu at gmail dot com
2012-08-17  6:31 ` tingw.liu at gmail dot com
2012-08-20  1:41 ` bugdal at aerifal dot cx
2012-08-21  6:07 ` tingw.liu at gmail dot com
2012-08-21 13:15 ` bugdal at aerifal dot cx
2012-08-22  0:33 ` tingw.liu at gmail dot com
2012-08-22  0:34 ` tingw.liu at gmail dot com
2012-08-22  1:08 ` bugdal at aerifal dot cx
2012-08-22  5:21 ` tingw.liu at gmail dot com
2012-08-22  5:24 ` tingw.liu at gmail dot com
2012-08-22  5:29 ` tingw.liu at gmail dot com
2013-01-09 16:31 ` schwab@linux-m68k.org
2013-01-10  5:03 ` tingw.liu at gmail dot com
2013-01-10  5:03 ` tingw.liu at gmail dot com
2014-06-17 18:36 ` fweimer at redhat dot com
2014-06-17 18:56 ` bugdal at aerifal dot cx [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=bug-14484-131-Z7bCqy7bvt@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).