IO-Uring Archive on
 help / color / Atom feed
From: Jens Axboe <>
Subject: [PATCHSET 0/2] Ensure all needed read/write data is stable
Date: Mon,  2 Dec 2019 15:30:59 -0700
Message-ID: <> (raw)

Currently we don't copy the associated iovecs when we punt to async
context, and this can prove problematic if the caller only ensures
the iovec is valid for the submission. This is a perfectly valid
assumption, and I think io_uring should make sure that this is safe
to do.

First patch is a prep patch, second patch adds the necessary support
for IORING_OP_READV and IORING_OP_WRITEV to handle this appropriately.
We really need to do the same for the other calls that pass in pointers
to structs, like sendmsg/recvmsg, connect, and accept. I will deal with
those next.

Also see:

Jens Axboe

             reply index

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-02 22:30 Jens Axboe [this message]
2019-12-02 22:31 ` [PATCH 1/2] io_uring: add general async offload context Jens Axboe
2019-12-02 22:31 ` [PATCH 2/2] io_uring: ensure async punted read/write requests copy iovec Jens Axboe

Reply instructions:

You may reply publically 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

IO-Uring Archive on

Archives are clonable:
	git clone --mirror io-uring/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 io-uring io-uring/ \
	public-inbox-index io-uring

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone