public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tingw.liu at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug nptl/14484] sem_timedwait always return -1 with errno 110 (ETIMEDOUT). Date: Tue, 21 Aug 2012 06:07:00 -0000 [thread overview] Message-ID: <bug-14484-131-QjJ9w0N2Pu@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-14484-131@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=14484 --- Comment #6 from tingweiliu <tingw.liu at gmail dot com> 2012-08-21 06:06:58 UTC --- (In reply to comment #5) > As far as I can tell this report is invalid and is just a case of the reporter > not understanding the interface. In particular, assuming the semaphore value is > initially zero and it's never posted: > 1. sem_timedwait should fail with ETIMEDOUT if the given time has already > passed when it's called. > 2. sem_timedwait should sleep until the given time, then fail with ETIMEDOUT, > if the given time is in the future. > 3. Signals that arrive during the wait should have no effect on sem_timedwait > unless the handler was installed without the SA_RESTART option. > Note that point 3 is not honored on most (all?) Linux versions; syscalls with > timeouts get interrupted with EINTR even if the signal handler was installed > with SA_RESTART. This is a bug in Linux, not glibc, and is impossible to fix at Maybe you should check the code in attachment. I have set a future time, and semaphore value is initially zero and it's never posted. So It should return with EINTR(errno=4). So anybody can tell me why it return with ETIMEOUT? > the libc level. > If you still believe there's a glibc bug here, please explain what you expect > the behavior to be in terms of the specification of the sem_timedwait function. > As I've said, I can't see any bug... -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next prev parent reply other threads:[~2012-08-21 6:07 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 [this message] 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
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-QjJ9w0N2Pu@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.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: linkBe 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).