From: Pavel Begunkov <[email protected]>
To: Jens Axboe <[email protected]>, [email protected]
Subject: Re: [PATCH 1/1] io_uring/rw: forbid multishot async reads
Date: Mon, 17 Feb 2025 14:08:35 +0000 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 2/17/25 13:58, Jens Axboe wrote:
> On 2/17/25 6:37 AM, Pavel Begunkov wrote:
>
> The kiocb semantics of ki_complete == NULL -> sync kiocb is also odd,
That's what is_sync_kiocb() does. Would be cleaner to use
init_sync_kiocb(), but there is a larger chance to do sth
wrong as it's reinitialises it entirely.
> but probably fine for this case as read mshot strictly deals with
> pollable files. Otherwise you'd just be blocking off this issue,
> regardless of whether or not IOCB_NOWAIT is set.
>
> In any case, it'd be much nicer to container this in io_read_mshot()
> where it arguably belongs, rather than sprinkle it in __io_read().
> Possible?
That's what I tried first, but __io_read() -> io_rw_init_file()
reinitialises it, so I don't see any good way without some
broader refactoring.
--
Pavel Begunkov
next prev parent reply other threads:[~2025-02-17 14:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-17 13:37 [PATCH 1/1] io_uring/rw: forbid multishot async reads Pavel Begunkov
2025-02-17 13:49 ` Pavel Begunkov
2025-02-17 13:58 ` Jens Axboe
2025-02-17 14:03 ` Pavel Begunkov
2025-02-17 14:04 ` Pavel Begunkov
2025-02-17 14:08 ` Pavel Begunkov [this message]
2025-02-17 15:37 ` Jens Axboe
2025-02-19 1:35 ` Pavel Begunkov
2025-02-17 14:12 ` Pavel Begunkov
2025-02-17 15:06 ` Jens Axboe
2025-02-17 15:33 ` Pavel Begunkov
2025-02-17 15:57 ` Jens Axboe
2025-02-17 17:51 ` Pavel Begunkov
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