From: Mukesh Ojha <quic_mojha@quicinc.com>
To: Waiman Long <longman@redhat.com>
Cc: <linux-kernel@vger.kernel.org>, <john.p.donnelly@oracle.com>,
Hillf Danton <hdanton@sina.com>,
Peter Zijlstra <peterz@infradead.org>,
Will Deacon <will@kernel.org>, Boqun Feng <boqun.feng@gmail.com>,
Ingo Molnar <mingo@redhat.com>
Subject: Re: [PATCH] locking/rwsem: Prevent non-first waiter from spinning in down_write() slowpath
Date: Fri, 30 Sep 2022 10:17:32 +0530 [thread overview]
Message-ID: <4e1697d7-9c13-12c9-74bc-dcb97ee2a659@quicinc.com> (raw)
In-Reply-To: <6530f135-e8ac-bb6c-4715-1ea8f76cf4c4@redhat.com>
Hi,
On 9/29/2022 11:36 PM, Waiman Long wrote:
> On 9/29/22 14:04, Waiman Long wrote:
>> A non-first waiter can potentially spin in the for loop of
>> rwsem_down_write_slowpath() without sleeping but fail to acquire the
>> lock even if the rwsem is free if the following sequence happens:
>>
>> Non-first waiter First waiter Lock holder
>> ---------------- ------------ -----------
>> Acquire wait_lock
>> rwsem_try_write_lock():
>> Set handoff bit if RT or
>> wait too long
>> Set waiter->handoff_set
>> Release wait_lock
>> Acquire wait_lock
>> Inherit waiter->handoff_set
>> Release wait_lock
>> Clear owner
>> Release lock
>> if (waiter.handoff_set) {
>> rwsem_spin_on_owner(();
>> if (OWNER_NULL)
>> goto trylock_again;
>> }
>> trylock_again:
>> Acquire wait_lock
>> rwsem_try_write_lock():
>> if (first->handoff_set && (waiter != first))
>> return false;
>> Release wait_lock
>>
>> It is especially problematic if the non-first waiter is an RT task and
>> it is running on the same CPU as the first waiter as this can lead to
>> live lock.
>>
>> Fixes: d257cc8cb8d5 ("locking/rwsem: Make handoff bit handling more
>> consistent")
>> Signed-off-by: Waiman Long <longman@redhat.com>
>> ---
>> kernel/locking/rwsem.c | 13 ++++++++++---
>> 1 file changed, 10 insertions(+), 3 deletions(-)
>
> Mukesh, can you test if this patch can fix the RT task lockup problem?
I will come back with the result.
Thank you.
>
> Thanks,
> Longman
>
next prev parent reply other threads:[~2022-09-30 4:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-29 18:04 Waiman Long
2022-09-29 18:06 ` Waiman Long
2022-09-30 4:47 ` Mukesh Ojha [this message]
2022-10-10 10:24 ` Mukesh Ojha
2022-10-10 16:57 ` Waiman Long
[not found] ` <03421f0e453143f6ae4a9a7a8a4f47f4@xiaomi.com>
[not found] ` <446288c6c7db4ab2b23f7041baa62335@xiaomi.com>
2022-10-12 13:21 ` Waiman Long
2022-09-29 21:15 ` John Donnelly
2022-09-30 1:09 ` Waiman Long
2022-09-30 4:46 ` Mukesh Ojha
2022-09-30 13:57 ` Waiman Long
2022-09-30 5:06 ` Mukesh Ojha
2022-09-30 14:08 ` Waiman Long
2022-09-30 16:03 ` Mukesh Ojha
[not found] <20221011104621.231-1-hdanton@sina.com>
2022-10-11 13:16 ` Mukesh Ojha
2022-10-12 13:16 ` Waiman Long
2022-10-12 13:14 ` Waiman Long
[not found] <20221012040410.403-1-hdanton@sina.com>
2022-10-12 13:19 ` Waiman Long
2022-10-12 13:42 ` Mukesh Ojha
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=4e1697d7-9c13-12c9-74bc-dcb97ee2a659@quicinc.com \
--to=quic_mojha@quicinc.com \
--cc=boqun.feng@gmail.com \
--cc=hdanton@sina.com \
--cc=john.p.donnelly@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=will@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
all inboxes | Powered by JetHome®