public inbox for [email protected]
 help / color / mirror / Atom feed
From: Pavel Begunkov <[email protected]>
To: Jens Axboe <[email protected]>,
	[email protected], [email protected]
Cc: Xan Charbonnet <[email protected]>,
	Salvatore Bonaccorso <[email protected]>
Subject: Re: [PATCH stable-6.1 1/1] io_uring: fix waiters missing wake ups
Date: Fri, 24 Jan 2025 21:23:07 +0000	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

On 1/24/25 20:47, Jens Axboe wrote:
> On 1/24/25 11:53 AM, Pavel Begunkov wrote:
>> [ upstream commit 3181e22fb79910c7071e84a43af93ac89e8a7106 ]
>>
>> There are reports of mariadb hangs, which is caused by a missing
>> barrier in the waking code resulting in waiters losing events.
>>
>> The problem was introduced in a backport
>> 3ab9326f93ec4 ("io_uring: wake up optimisations"),
>> and the change restores the barrier present in the original commit
>> 3ab9326f93ec4 ("io_uring: wake up optimisations")
>>
>> Reported by: Xan Charbonnet <[email protected]>
>> Fixes: 3ab9326f93ec4 ("io_uring: wake up optimisations")
>> Link: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1093243#99
>> Signed-off-by: Pavel Begunkov <[email protected]>
>> ---
>>   io_uring/io_uring.c | 4 +++-
>>   1 file changed, 3 insertions(+), 1 deletion(-)
>>
>> diff --git a/io_uring/io_uring.c b/io_uring/io_uring.c
>> index 9b58ba4616d40..e5a8ee944ef59 100644
>> --- a/io_uring/io_uring.c
>> +++ b/io_uring/io_uring.c
>> @@ -592,8 +592,10 @@ static inline void __io_cq_unlock_post_flush(struct io_ring_ctx *ctx)
>>   	io_commit_cqring(ctx);
>>   	spin_unlock(&ctx->completion_lock);
>>   	io_commit_cqring_flush(ctx);
>> -	if (!(ctx->flags & IORING_SETUP_DEFER_TASKRUN))
>> +	if (!(ctx->flags & IORING_SETUP_DEFER_TASKRUN)) {
>> +		smp_mb();
>>   		__io_cqring_wake(ctx);
>> +	}
>>   }
> 
> We could probably just s/__io_cqring_wake/io_cqring_wake here to get
> the same effect. Not that it really matters, it's just simpler.

Right, I noticed but am keeping it closer to the original
in case we'd need to port more in the future.

-- 
Pavel Begunkov


  reply	other threads:[~2025-01-24 21:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-24 18:53 [PATCH stable-6.1 1/1] io_uring: fix waiters missing wake ups Pavel Begunkov
2025-01-24 20:47 ` Jens Axboe
2025-01-24 21:23   ` Pavel Begunkov [this message]
2025-01-24 21:23     ` Jens Axboe
2025-01-25  6:59 ` lizetao
2025-01-30  8:51   ` Greg KH

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 \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /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