All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Andrew Halaney <ahalaney@redhat.com>
Cc: bigeasy@linutronix.de, linux-kernel@vger.kernel.org,
	linux-rt-users@vger.kernel.org, Chunyu Hu <chuhu@redhat.com>,
	stable-rt@vger.kernel.org
Subject: Re: [RT PATCH] locking/rwsem-rt: Remove might_sleep() in __up_read()
Date: Fri, 09 Jul 2021 15:48:33 +0200	[thread overview]
Message-ID: <87bl7boaxa.ffs@nanos.tec.linutronix.de> (raw)
In-Reply-To: <20210708195125.zxqsxy5bpccgxb2n@halaneylaptop>

Andrew,

On Thu, Jul 08 2021 at 14:51, Andrew Halaney wrote:

Cc+ stable-rt folks and leave context untrimmed.

> On Mon, Apr 26, 2021 at 08:16:34PM +0200, Thomas Gleixner wrote:
>> On Mon, Apr 26 2021 at 11:42, Andrew Halaney wrote:
>> > On Tue, Apr 06, 2021 at 05:19:52PM -0500, Andrew Halaney wrote:
>> >> There's no chance of sleeping here, the reader is giving up the
>> >> lock and possibly waking up the writer who is waiting on it.
>> >> 
>> >> Reported-by: Chunyu Hu <chuhu@redhat.com>
>> >> Signed-off-by: Andrew Halaney <ahalaney@redhat.com>
>> >> ---
>> >> Hello,
>> >> 
>> >> I ran into a warning caused by this, and I think the warning is
>> >> incorrect. Please let me know if I'm wrong!
>> >> I'm working off of linux-5.12.y-rt, but this applies cleanly to older
>> >> stable branches as well.
>> >>
>> >> Thanks,
>> >> Andrew
>> >> 
>> >>  kernel/locking/rwsem-rt.c | 1 -
>> >>  1 file changed, 1 deletion(-)
>> >> 
>> >> diff --git a/kernel/locking/rwsem-rt.c b/kernel/locking/rwsem-rt.c
>> >> index 274172d5bb3a..b61edc4dcb73 100644
>> >> --- a/kernel/locking/rwsem-rt.c
>> >> +++ b/kernel/locking/rwsem-rt.c
>> >> @@ -198,7 +198,6 @@ void __up_read(struct rw_semaphore *sem)
>> >>  	if (!atomic_dec_and_test(&sem->readers))
>> >>  		return;
>> >>  
>> >> -	might_sleep();
>> >>  	raw_spin_lock_irq(&m->wait_lock);
>> >>  	/*
>> >>  	 * Wake the writer, i.e. the rtmutex owner. It might release the
>> >> -- 
>> >> 2.30.2
>> >
>> > Just a gentle follow up, any feedback?
>> 
>> Looks correct. Will go into the next rt-release.
>> 
>> Thanks,
>> 
>>         tglx
>> 
>
> Hi Thomas,
>
> I see a new release (v5.13-rt1) was created, and with it rwsem
> was overhauled entirely making this patch pointless for linux-rt-devel.
>
> That being said, it's a little unclear to me how RT only patches
> make their way to the maintained branches over in linux-stable-rt.
> I think it should be applied to:
>  v4.9-rt
>  v4.14-rt
>  v4.19-rt
>  v5.4-rt
>  v5.10-rt
> to remove the incorrect warning, unless those branches plan to backport
> the latest RT patchset with the new rwsem implementation. Is there a
> proper way for me signal that?

See Cc.

Thanks,

        tglx

      reply	other threads:[~2021-07-09 13:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-06 22:19 [RT PATCH] locking/rwsem-rt: Remove might_sleep() in __up_read() Andrew Halaney
2021-04-26 16:42 ` Andrew Halaney
2021-04-26 18:16   ` Thomas Gleixner
2021-07-08 19:51     ` Andrew Halaney
2021-07-09 13:48       ` Thomas Gleixner [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=87bl7boaxa.ffs@nanos.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=ahalaney@redhat.com \
    --cc=bigeasy@linutronix.de \
    --cc=chuhu@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=stable-rt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.