LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Mike Galbraith <umgwanakikbuti@gmail.com>
Cc: Gustavo Bittencourt <gbitten@gmail.com>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
rostedt@goodmis.org, John Kacur <jkacur@redhat.com>
Subject: Re: [ANNOUNCE] 3.18.7-rt2
Date: Thu, 26 Feb 2015 11:53:04 +0100 [thread overview]
Message-ID: <20150226105304.GB12992@linutronix.de> (raw)
In-Reply-To: <1424937725.3622.31.camel@gmail.com>
* Mike Galbraith | 2015-02-26 09:02:05 [+0100]:
>I found what was breaking my core2 lappy in 4.0-rt as well, namely the
4.0-rt? So you are a time traveler?
>locking, ww_mutex: fix ww_mutex vs self-deadlock
>
>If the caller already holds the mutex, task_blocks_on_rt_mutex()
>returns -EDEADLK, we proceed directly to rt_mutex_handle_deadlock()
>where it's instant game over.
The EDDEADLK / ELREADY seem to got broken duering the rtmutex rework.
Now I see:
| Wound/wait tests |
---------------------
ww api failures: ok | ok | ok |
ww contexts mixing: ok | ok |
finishing ww context: ok | ok | ok | ok |
locking mismatches: ok | ok | ok |
EDEADLK handling: ok | ok | ok | ok | ok | ok | ok | ok | ok | ok |
spinlock nest unlocked: ok |
with no backtrace from the ww code which I haven't seen before that
patch. Applied.
Sebastian
next prev parent reply other threads:[~2015-02-26 10:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-23 9:06 Sebastian Andrzej Siewior
2015-02-24 13:41 ` Mike Galbraith
2015-02-24 14:13 ` Mike Galbraith
2015-02-24 16:19 ` Gustavo Bittencourt
2015-02-24 17:50 ` Mike Galbraith
2015-02-24 20:00 ` Gustavo Bittencourt
2015-02-25 2:27 ` Mike Galbraith
2015-02-26 8:02 ` Mike Galbraith
2015-02-26 10:53 ` Sebastian Andrzej Siewior [this message]
2015-02-26 11:30 ` Mike Galbraith
2015-02-26 16:40 ` Gustavo Bittencourt
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=20150226105304.GB12992@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=gbitten@gmail.com \
--cc=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=umgwanakikbuti@gmail.com \
--subject='Re: [ANNOUNCE] 3.18.7-rt2' \
/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
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 NNTP newsgroup(s).