From: Dave Jones <davej@redhat.com>
To: Davidlohr Bueso <davidlohr@hp.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
peterz@infradead.org,
Linus Torvalds <torvalds@linux-foundation.org>,
tglx@linutronix.de
Subject: Re: [3.15-rc3] rtmutex-debug assertion.
Date: Tue, 29 Apr 2014 23:40:23 -0400 [thread overview]
Message-ID: <20140430034023.GA12319@redhat.com> (raw)
In-Reply-To: <1398824670.2522.19.camel@buesod1.americas.hpqcorp.net>
On Tue, Apr 29, 2014 at 07:24:30PM -0700, Davidlohr Bueso wrote:
> > futex(uaddr=0x7f55ff8c4000, op=0x6, val=0x200000006223800b, utime=0x7f55ff8c4000, uaddr2=0x7f55ff8c4000, val3=-123)
>
> Perhaps because of chance. Even for pi futexes, if the lock is
> uncontended, the kernel will never take part.
Ok, once more..
futex(uaddr=0x25fe000[page_rand], op=0x6, val=0xffff4e2644b3dfcb, utime=0x25fe004[page_rand], uaddr2=0x25fe008[page_rand], val3=0xffffffff440fcd80)
FUTEX_LOCK_PI again.
> Would reverting commit c365c292d059 (sched: Consider pi boosting in
> setscheduler()) fix this?
I'll try and write a standalone reproducer in the morning.
Then I'll be able to tell you for sure if that commit is good/bad.
Dave
next prev parent reply other threads:[~2014-04-30 3:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-29 15:16 [3.15-rc3] rtmutex-debug assertion Dave Jones
2014-04-30 0:14 ` Dave Jones
2014-04-30 2:24 ` Davidlohr Bueso
2014-04-30 3:40 ` Dave Jones [this message]
2014-04-30 8:24 ` Thomas Gleixner
2014-04-30 9:13 ` Thomas Gleixner
2014-05-02 4:56 ` Dave Jones
2014-05-05 18:08 ` Thomas Gleixner
[not found] ` <20140505182942.GA19129@redhat.com>
2014-05-08 15:28 ` Thomas Gleixner
2014-05-08 19:26 ` Dave Jones
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=20140430034023.GA12319@redhat.com \
--to=davej@redhat.com \
--cc=davidlohr@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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