From: Hao Xu <[email protected]>
To: io-uring <[email protected]>
Cc: Jens Axboe <[email protected]>, Pavel Begunkov <[email protected]>
Subject: Possible bug for ring-mapped provided buffer
Date: Thu, 9 Jun 2022 15:53:57 +0800 [thread overview]
Message-ID: <[email protected]> (raw)
Hi all,
I haven't done tests to demonstrate it. It is for partial io case, we
don't consume/release the buffer before arm_poll in ring-mapped mode.
But seems we should? Otherwise ring head isn't moved and other requests
may take that buffer. What do I miss?
Regards,
Hao
next reply other threads:[~2022-06-09 7:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 7:53 Hao Xu [this message]
2022-06-09 9:33 ` Possible bug for ring-mapped provided buffer Hao Xu
2022-06-09 9:54 ` Hao Xu
2022-06-09 10:06 ` Jens Axboe
2022-06-09 10:14 ` Hao Xu
2022-06-09 10:19 ` Jens Axboe
2022-06-09 10:32 ` Hao Xu
2022-06-09 15:06 ` Jens Axboe
2022-06-09 16:08 ` Hao Xu
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] \
/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