From: Jens Axboe <axboe@kernel.dk>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Peter Zijlstra <peterz@infradead.org>,
Daniel Wagner <wagi@monom.org>,
Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
linux-rt-users@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [ANNOUNCE] v5.14-rc4-rt4
Date: Wed, 4 Aug 2021 09:39:30 -0600 [thread overview]
Message-ID: <f2d0a028-fe85-28ff-9cea-8ab1d26a15d0@kernel.dk> (raw)
In-Reply-To: <20210804153308.oasahcxjmcw7vivo@linutronix.de>
On 8/4/21 9:33 AM, Sebastian Andrzej Siewior wrote:
> On 2021-08-04 08:23:55 [-0600], Jens Axboe wrote:
>> Totally untested, but I think the principle is sound. I'll run it through
>> some testing.
>
> This is needed:
>
> diff --git a/fs/io-wq.c b/fs/io-wq.c
> index 1192ee2abd982..77ec6896edaa5 100644
> --- a/fs/io-wq.c
> +++ b/fs/io-wq.c
> @@ -428,9 +428,9 @@ static struct io_wq_work *io_get_next_work(struct io_wqe *wqe)
> }
>
> if (stall_hash != -1U) {
> - raw_spin_unlock(&wqe->lock);
> + raw_spin_unlock_irq(&wqe->lock);
> io_wait_on_hash(wqe, stall_hash);
> - raw_spin_lock(&wqe->lock);
> + raw_spin_lock_irq(&wqe->lock);
> }
>
> return NULL;
>
>
> otherwise the spinlock_t lock in io_wait_on_hash() is acquired with
> disabled interrupts which is a no-no on -RT.
> With that it all looks good as far as I can tell.
> Thank you.
I'm confused, the waitqueue locks are always IRQ disabling.
--
Jens Axboe
next prev parent reply other threads:[~2021-08-04 15:39 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-02 16:27 [ANNOUNCE] v5.14-rc4-rt4 Sebastian Andrzej Siewior
2021-08-04 8:24 ` Daniel Wagner
2021-08-04 10:43 ` Sebastian Andrzej Siewior
2021-08-04 10:48 ` Sebastian Andrzej Siewior
2021-08-04 11:00 ` Sebastian Andrzej Siewior
2021-08-04 13:17 ` Peter Zijlstra
2021-08-04 13:32 ` Jens Axboe
2021-08-04 14:23 ` Jens Axboe
2021-08-04 15:33 ` Sebastian Andrzej Siewior
2021-08-04 15:39 ` Jens Axboe [this message]
2021-08-04 15:47 ` Sebastian Andrzej Siewior
2021-08-04 15:49 ` Jens Axboe
2021-08-04 15:57 ` Sebastian Andrzej Siewior
2021-08-04 16:05 ` Jens Axboe
2021-08-04 16:20 ` Sebastian Andrzej Siewior
2021-08-04 16:20 ` Jens Axboe
2021-08-04 16:20 ` Steven Rostedt
2021-08-04 16:22 ` Jens Axboe
2021-08-04 16:47 ` Sebastian Andrzej Siewior
2021-08-04 16:57 ` Jens Axboe
2021-08-04 17:02 ` Sebastian Andrzej Siewior
2021-08-10 7:40 ` Sebastian Andrzej Siewior
2021-08-10 11:22 ` [PATCH] io-wq: remove GFP_ATOMIC allocation off schedule out path kernel test robot
2021-08-10 15:22 ` kernel test robot
2021-08-04 16:17 ` [ANNOUNCE] v5.14-rc4-rt4 Steven Rostedt
2021-08-04 16:22 ` Sebastian Andrzej Siewior
2021-08-04 16:25 ` Steven Rostedt
2021-08-04 16:31 ` Sebastian Andrzej Siewior
2021-08-04 16:47 ` Steven Rostedt
2021-08-04 16:57 ` 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=f2d0a028-fe85-28ff-9cea-8ab1d26a15d0@kernel.dk \
--to=axboe@kernel.dk \
--cc=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=wagi@monom.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