From: Jens Axboe <[email protected]>
To: [email protected]
Cc: [email protected]
Subject: [PATCH 0/2] Pol fixups
Date: Tue, 10 Jan 2023 11:00:53 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
Hi,
Patch 1 just adds support for fdinfo outputting state of the locked
poll hash table, something which was forgotten when that support was
added earlier.
Patch 2 fixes a race where multiple requests on the same poll waitqueue
may get woken and not properly retried. This causes those requests to
potentially never get woken again, if we race.
--
Jens Axboe
next reply other threads:[~2023-01-10 18:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 18:00 Jens Axboe [this message]
2023-01-10 18:00 ` [PATCH 1/2] io_uring/fdinfo: include locked hash table in fdinfo output Jens Axboe
2023-01-10 18:00 ` [PATCH 2/2] io_uring/poll: attempt request issue after racy poll wakeup Jens Axboe
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] \
/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