From: Mart van de Wege <mvdwege@mail.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Marcel Holtmann <marcel@holtmann.org>,
Johan Hedberg <johan.hedberg@intel.com>,
Gustavo Padovan <gustavo@padovan.org>,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-rt-users@vger.kernel.org, tglx@linutronix.de,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: Possible BT deadlock due to recursive read locking (Was: Re: kernel BUG at kernel/locking/rtmutex.c:1059)
Date: Sat, 2 Sep 2017 09:27:07 +0200 [thread overview]
Message-ID: <20170902092707.1e8800bb@mail.com> (raw)
In-Reply-To: <20170901105107.753617a1@gmail.com>
On Fri, 1 Sep 2017 10:51:07 +0200
Mart van de Wege <mvdwege@gmail.com> wrote:
> On Thu, 31 Aug 2017 16:52:12 +0200
> Sebastian Andrzej Siewior <bigeasy@linutronix.de> wrote:
>
> > On 2017-08-30 23:25:53 [+0200], Mart van de Wege wrote:
> > > Hi,
> > Hi,
> >
> > > The issue persists up to v4.11.12-rt10
> > Does
> > CONFIG_RWLOCK_RT_READER_BIASED=y
> > make it go away?
> >
> Yes, that does make it go away. -rt8 now boots cleanly, and works
> fine. Building -rt10 now to be sure.
>
Confirm that as of 4.11.12-rt11 the deadlock still goes away when
enabling CONFIG_RWLOCK_RT_READER_BIASED
Mart
next prev parent reply other threads:[~2017-09-02 7:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <86val4928u.fsf@gaheris.avalon.lan>
2017-08-31 14:52 ` Possible BT deadlock due to recursive read locking (Was: Re: kernel BUG at kernel/locking/rtmutex.c:1059) Sebastian Andrzej Siewior
2017-08-31 14:56 ` Thomas Gleixner
2017-09-01 8:51 ` Mart van de Wege
2017-09-02 7:27 ` Mart van de Wege [this message]
2017-09-21 13:51 ` [PATCH] Bluetooth: avoid recursive locking in hci_send_to_channel() Sebastian Andrzej Siewior
2017-09-24 14:53 ` Mart van de Wege
2017-10-30 8:05 ` Marcel Holtmann
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=20170902092707.1e8800bb@mail.com \
--to=mvdwege@mail.com \
--cc=bigeasy@linutronix.de \
--cc=gustavo@padovan.org \
--cc=johan.hedberg@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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).