public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "yeatesrichardr at johndeere dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug nptl/26801] pthread_mutex_clocklock with CLOCK_MONOTONIC can fail on PI futexs
Date: Wed, 28 Oct 2020 13:59:19 +0000	[thread overview]
Message-ID: <bug-26801-131-vlozzKOSQD@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26801-131@http.sourceware.org/bugzilla/>

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

--- Comment #1 from Ric Yeates <yeatesrichardr at johndeere dot com> ---
Forgot to include example output.

$ futex_bug
FAILURE: ETIMEDOUT should have been returned after 10 or more seconds, returned
after 0 seconds.

$ uname -a
Linux PCMA4MA000002.local.domain 5.4.47-2.2.0 #1 SMP PREEMPT Mon Oct 26
23:52:12 UTC 2020 aarch64 GNU/Linux

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

  reply	other threads:[~2020-10-28 13:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-28 13:54 [Bug nptl/26801] New: " yeatesrichardr at johndeere dot com
2020-10-28 13:59 ` yeatesrichardr at johndeere dot com [this message]
2020-10-28 14:01 ` [Bug nptl/26801] pthread_mutex_clocklock with CLOCK_MONOTONIC can fail on PI mutexes yeatesrichardr at johndeere dot com
2020-10-28 17:33 ` yeatesrichardr at johndeere dot com
2020-10-28 20:02 ` adhemerval.zanella at linaro dot org
2020-11-25 15:31 ` adhemerval.zanella at linaro dot org

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-26801-131-vlozzKOSQD@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).