public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Torvald Riegel <triegel@redhat.com>
To: Martin Galvan <omgalvan.86@gmail.com>
Cc: siddhesh@sourceware.org, Joseph Myers <joseph@codesourcery.com>,
	libc-alpha@sourceware.org
Subject: Re: [PATCH v11] Add pretty printers for the NPTL lock types
Date: Fri, 06 Jan 2017 21:58:00 -0000	[thread overview]
Message-ID: <1483739904.5606.126.camel@redhat.com> (raw)
In-Reply-To: <CAN19L9E9FEjfmjaxiW-Mr4ueax-Raao+b_MJE6AMmWVN8T15eg@mail.gmail.com>

On Fri, 2016-12-23 at 16:37 -0300, Martin Galvan wrote:
> 2016-12-23 15:47 GMT-03:00 Torvald Riegel <triegel@redhat.com>:
> >   Status = Locked, possibly with no waiters, Owner ID = 0, Robust = No,
> 
> That's odd, IIRC locked mutexes always record their owner's ID. I
> assume manually printing mutex->__data.__owner at that point shows 0
> too, right?

This may be related to lock elision.  In a build with lock elision
disabled, I didn't see the failure.  The next build with lock elision
enabled again showed the failure.

Did you test with or without lock elision?

  parent reply	other threads:[~2017-01-06 21:58 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-27  3:04 Martin Galvan
2016-11-28 12:11 ` Stefan Liebler
2016-11-28 16:00   ` Martin Galvan
2016-12-04 12:41 ` Siddhesh Poyarekar
2016-12-04 20:56   ` Martin Galvan
2016-12-08 13:36   ` Siddhesh Poyarekar
2016-12-08 18:56     ` Joseph Myers
2016-12-08 21:01       ` Martin Galvan
2016-12-12 20:55       ` Martin Galvan
2016-12-12 23:15         ` Joseph Myers
2016-12-12 23:21           ` Martin Galvan
2016-12-14 18:20         ` Joseph Myers
2016-12-14 19:46           ` Martin Galvan
2016-12-17 18:10             ` Martin Galvan
2016-12-17 19:07               ` Siddhesh Poyarekar
2016-12-17 19:09                 ` Martin Galvan
2016-12-22 16:35                   ` Torvald Riegel
2016-12-22 16:44                     ` Martin Galvan
2016-12-22 22:50                       ` Torvald Riegel
2016-12-22 23:40                         ` Martin Galvan
2016-12-23 17:05                           ` Torvald Riegel
2016-12-23 17:40                             ` Martin Galvan
2016-12-23 18:05                               ` Martin Galvan
2016-12-23 18:48                               ` Torvald Riegel
2016-12-23 19:38                                 ` Martin Galvan
2016-12-26 14:17                                   ` Martin Galvan
2017-01-02 12:48                                     ` Martin Galvan
2017-01-02 13:51                                       ` Joseph Myers
2017-01-02 14:35                                         ` Martin Galvan
2017-01-02 15:47                                           ` Torvald Riegel
2017-01-02 21:51                                           ` Joseph Myers
2017-01-03  7:27                                             ` Siddhesh Poyarekar
2017-01-06 21:58                                   ` Torvald Riegel [this message]
2017-01-09 19:37                                     ` Martin Galvan

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=1483739904.5606.126.camel@redhat.com \
    --to=triegel@redhat.com \
    --cc=joseph@codesourcery.com \
    --cc=libc-alpha@sourceware.org \
    --cc=omgalvan.86@gmail.com \
    --cc=siddhesh@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).