From: Jens Axboe <axboe@kernel.dk>
To: agxr <agxr@disroot.org>, io-uring@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Josef Bacik <josef@toxicpanda.com>
Subject: Re: [PATCH 0/2] io_uring/cancel: futex and waitid cancel results
Date: Sat, 24 Oct 2026 21:23:29 -0600 [thread overview]
Message-ID: <9c1cd77b-8a00-49c8-b3c6-625c0ecc6694@kernel.dk> (raw)
In-Reply-To: <20261024163259.19372-1-agxr@disroot.org>
On 10/24/26 10:31 AM, agxr wrote:
> io_futex_cancel() and io_waitid_cancel() return the number of requests
> they canceled, where the rest of what io_try_cancel() calls returns 0.
> Commit c74193430feb ("io_uring/timeout: don't end a linked timeout with
> 1") took care of what that did to a linked timeout.
>
> liburing's futex, waitid, io-cancel, sync-cancel, poll-cancel-all,
> cancel-race, futex-kill, link-timeout, timeout and poll-cancel tests
> pass on both patched kernels. Unchanged liburing tests pass with patch
> 1 and fail with patch 2, where they check for the 1.
>
> agxr (2):
> io_uring/cancel: count all canceled futex and waitid requests on
> CANCEL_ALL
> io_uring/cancel: complete single futex or waitid cancel with 0
>
> io_uring/cancel.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
I'll take a look at these - but please note, that:
Signed-off-by: agxr <agxr@disroot.org>
is not going to be adequate for the kernel, we generally ask for
a known identity. That's either a real name or at least a well
known identity, above is neither of those.
--
Jens Axboe
prev parent reply other threads:[~2026-10-25 3:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-24 16:31 agxr
2026-10-24 16:31 ` [PATCH 1/2] io_uring/cancel: count all canceled futex and waitid requests on CANCEL_ALL agxr
2026-10-24 16:31 ` [PATCH 2/2] io_uring/cancel: complete single futex or waitid cancel with 0 agxr
2026-10-25 3:23 ` Jens Axboe [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=9c1cd77b-8a00-49c8-b3c6-625c0ecc6694@kernel.dk \
--to=axboe@kernel.dk \
--cc=agxr@disroot.org \
--cc=io-uring@vger.kernel.org \
--cc=josef@toxicpanda.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®