From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Crystal Wood <swood@redhat.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
John Keeping <john@metanate.com>,
linux-rt-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: rtmutex, pi_blocked_on, and blk_flush_plug()
Date: Thu, 16 Feb 2023 16:05:45 +0100 [thread overview]
Message-ID: <Y+5GScI95xYeQPvf@linutronix.de> (raw)
In-Reply-To: <Y+47FVJ+hI+NA2In@linutronix.de>
On 2023-02-16 15:18:03 [+0100], To Crystal Wood wrote:
> On 2023-02-09 22:31:57 [-0600], Crystal Wood wrote:
> > Hello!
Hi,
> - spinlock_t invokes schedule_rtlock() which avoids sched_submit_work().
> This is the behaviour as with !RT because it spins and does not submit
> work either.
> rwlock_t should be have the same way but invokes schedule() instead.
> This looks wrong. And it could deadlock in sched_submit_work().
I have to correct myself. Also for rwlock_t it uses schedule_rtlock()
which means it does not invoke sched_submit_work().
There there I don't expect any deadlock here.
> > -Crystal
Sebastian
next prev parent reply other threads:[~2023-02-16 15:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 4:31 rtmutex, pi_blocked_on, and blk_flush_plug() Crystal Wood
2023-02-16 14:17 ` Sebastian Andrzej Siewior
2023-02-16 15:05 ` Sebastian Andrzej Siewior [this message]
2023-02-20 9:49 ` Thomas Gleixner
2023-02-20 11:04 ` Sebastian Andrzej Siewior
2023-02-20 11:42 ` Sebastian Andrzej Siewior
2023-02-20 18:21 ` Thomas Gleixner
2023-03-05 5:39 ` Crystal Wood
2023-03-22 16:41 ` Sebastian Andrzej Siewior
2023-03-23 14:50 ` Sebastian Andrzej Siewior
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=Y+5GScI95xYeQPvf@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=john@metanate.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=swood@redhat.com \
--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