From: Udo van den Heuvel <udovdh@xs4all.nl>
To: Juri Lelli <juri.lelli@gmail.com>
Cc: RT <linux-rt-users@vger.kernel.org>
Subject: Re: 5.2.21-rt13 WARN_ON(rt_mutex_owner(lock) != current)
Date: Fri, 29 Nov 2019 13:16:02 +0100 [thread overview]
Message-ID: <646d19b9-7a74-5b3a-b272-860d565e62c9@xs4all.nl> (raw)
In-Reply-To: <20191125071729.GH23227@localhost.localdomain>
On 25-11-2019 08:17, Juri Lelli wrote:
> Peter is working on rewriting percpu_rwsem implementation to fix it.
>
> https://lore.kernel.org/lkml/20191113102115.116470462@infradead.org/
How/when will that work reach us?
The issue is very reproducible here and affects stability a tad too much.
A patch to fix this would be quite useful...
Thanks in advance....!
Kind regards,
Udo
prev parent reply other threads:[~2019-11-29 12:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-24 6:08 5.2.21-rt13 WARN_ON(rt_mutex_owner(lock) != current) Udo van den Heuvel
2019-11-25 7:17 ` Juri Lelli
2019-11-29 12:16 ` Udo van den Heuvel [this message]
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=646d19b9-7a74-5b3a-b272-860d565e62c9@xs4all.nl \
--to=udovdh@xs4all.nl \
--cc=juri.lelli@gmail.com \
--cc=linux-rt-users@vger.kernel.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 NNTP newsgroup(s).