public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: Gabriel Krisman Bertazi <krisman@suse.de>
To: Jens Axboe <axboe@kernel.dk>
Cc: io-uring@vger.kernel.org
Subject: Re: [PATCH 5/6] io_uring/futex: ensure partial wakes are appropriately dequeued
Date: Tue, 21 Apr 2026 13:11:24 -0400	[thread overview]
Message-ID: <87y0igp7b7.fsf@mailhost.krisman.be> (raw)
In-Reply-To: <20260421135626.581917-6-axboe@kernel.dk> (Jens Axboe's message of "Tue, 21 Apr 2026 07:51:42 -0600")

Jens Axboe <axboe@kernel.dk> writes:

> If a FUTEX_WAITV vectored operation is only partially woken, we
> should call __futex_wake_mark() on the queue to account for that.
> If not, then a later wakeup will wake the same entry, rather than
> the next one in line.
>
> Fixes: 8f350194d5cfd ("io_uring: add support for vectored futex waits")
> Signed-off-by: Jens Axboe <axboe@kernel.dk>

Reviewed-by: Gabriel Krisman Bertazi <krisman@suse.de>

> ---
>  io_uring/futex.c | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/io_uring/futex.c b/io_uring/futex.c
> index fd503c24b428..9cc1788ef4c6 100644
> --- a/io_uring/futex.c
> +++ b/io_uring/futex.c
> @@ -159,8 +159,10 @@ static void io_futex_wakev_fn(struct wake_q_head *wake_q, struct futex_q *q)
>  	struct io_kiocb *req = q->wake_data;
>  	struct io_futexv_data *ifd = req->async_data;
>  
> -	if (!io_futexv_claim(ifd))
> +	if (!io_futexv_claim(ifd)) {
> +		__futex_wake_mark(q);
>  		return;
> +	}
>  	if (unlikely(!__futex_wake_mark(q)))
>  		return;

-- 
Gabriel Krisman Bertazi

  reply	other threads:[~2026-04-21 17:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-21 13:51 [PATCHSET 0/6] Various bug fixes Jens Axboe
2026-04-21 13:51 ` [PATCH 1/6] io_uring: fix spurious fput in registered ring path Jens Axboe
2026-04-21 17:05   ` Gabriel Krisman Bertazi
2026-04-21 13:51 ` [PATCH 2/6] io_uring/rsrc: unify nospec indexing for direct descriptors Jens Axboe
2026-04-21 17:09   ` Gabriel Krisman Bertazi
2026-04-21 13:51 ` [PATCH 3/6] io_uring/rsrc: use kvfree() for the imu cache Jens Axboe
2026-04-21 13:51 ` [PATCH 4/6] io_uring/rw: add defensive hardening for negative kbuf lengths Jens Axboe
2026-04-21 17:10   ` Gabriel Krisman Bertazi
2026-04-21 13:51 ` [PATCH 5/6] io_uring/futex: ensure partial wakes are appropriately dequeued Jens Axboe
2026-04-21 17:11   ` Gabriel Krisman Bertazi [this message]
2026-04-21 13:51 ` [PATCH 6/6] io_uring/register: fix ring resizing with mixed/large SQEs/CQEs Jens Axboe
2026-04-21 17:12   ` Gabriel Krisman Bertazi

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=87y0igp7b7.fsf@mailhost.krisman.be \
    --to=krisman@suse.de \
    --cc=axboe@kernel.dk \
    --cc=io-uring@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox