All of lore.kernel.org
 help / color / mirror / Atom feed
From: nick@nickhill.org
To: io-uring@vger.kernel.org
Subject: WRITEV with IOSQE_ASYNC broken?
Date: Fri, 04 Sep 2020 20:22:09 -0700	[thread overview]
Message-ID: <382946a1d3513fbb1354c8e2c875e036@nickhill.org> (raw)

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.

Sorry if I've made a mistake somehow, and thanks for all the great work 
on this game-changing feature!

Nick

             reply	other threads:[~2020-09-05  3:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-05  3:22 nick [this message]
2020-09-05  3:53 ` WRITEV with IOSQE_ASYNC broken? Jens Axboe
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 \
    --in-reply-to=382946a1d3513fbb1354c8e2c875e036@nickhill.org \
    --to=nick@nickhill.org \
    --cc=io-uring@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.