From: Jens Axboe <[email protected]>
To: [email protected], [email protected]
Subject: Re: WRITEV with IOSQE_ASYNC broken?
Date: Fri, 4 Sep 2020 21:53:48 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 9/4/20 9:22 PM, [email protected] wrote:
> Hi,
>
> I am helping out with the netty io_uring integration, and came across
> some strange behaviour which seems like it might be a bug related to
> async offload of read/write iovecs.
>
> Basically a WRITEV SQE seems to fail reliably with -BADADDRESS when the
> IOSQE_ASYNC flag is set but works fine otherwise (everything else the
> same). This is with 5.9.0-rc3.
Do you see it just on 5.9-rc3, or also 5.8? Just curious... But that is
very odd in any case, ASYNC writev is even part of the regular tests.
Any sort of deferral, be it explicit via ASYNC or implicit through
needing to retry, saves all the needed details to retry without
needing any of the original context.
Can you narrow down what exactly is being written - like file type,
buffered/O_DIRECT, etc. What file system, what device is hosting it.
The more details the better, will help me narrow down what is going on.
> Sorry if I've made a mistake somehow, and thanks for all the great work
> on this game-changing feature!
Thanks! Let's get to the bottom of this.
--
Jens Axboe
next prev parent reply other threads:[~2020-09-05 3:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-05 3:22 WRITEV with IOSQE_ASYNC broken? nick
2020-09-05 3:53 ` Jens Axboe [this message]
2020-09-05 3:57 ` Jens Axboe
2020-09-05 4:35 ` Jens Axboe
2020-09-05 5:50 ` Pavel Begunkov
2020-09-05 8:24 ` nick
2020-09-05 8:26 ` Norman Maurer
2020-09-05 14:28 ` Norman Maurer
2020-09-05 15:02 ` Jens Axboe
2020-09-05 15:10 ` Jens Axboe
2020-09-05 5:04 ` nick
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