All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jann Horn <jannh@google.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-aio@kvack.org, linux-block@vger.kernel.org,
	linux-man <linux-man@vger.kernel.org>,
	Linux API <linux-api@vger.kernel.org>,
	hch@lst.de, jmoyer@redhat.com, Avi Kivity <avi@scylladb.com>
Subject: Re: [PATCH 05/18] Add io_uring IO interface
Date: Tue, 29 Jan 2019 16:56:31 +0100	[thread overview]
Message-ID: <CAG48ez0sNBjgW7ynpNC+sir-_AuccY1sKguiD+VAXvL9-j4iag@mail.gmail.com> (raw)
In-Reply-To: <b5902860-30a9-3dc9-b513-3d892afdc51b@kernel.dk>

On Tue, Jan 29, 2019 at 4:46 AM Jens Axboe <axboe@kernel.dk> wrote:
> On 1/28/19 7:21 PM, Jann Horn wrote:
> > Please create a local copy of the request before parsing it to keep
> > the data from changing under you. Additionally, it might make sense to
> > annotate every pointer to shared memory with a comment, or something
> > like that, to ensure that anyone looking at the code can immediately
> > see for which pointers special caution is required on access.
>
> I took a look at the viability of NOT having to local copy the data, and
> I don't think it's too bad. Local copy has a noticeable impact on the
> performance, hence I'd really (REALLY) like to avoid it.
>
> Here's something on top of the current git branch. I think I even went a
> bit too far in some areas, but it should hopefully catch the cases where
> we might end up double evaluating the parts of the sqe that we depend
> on. For most of the sqe reading we don't really care too much. For
> instance, the sqe->user_data. If the app changes this field, then it
> just gets whatever passed back in cqe->user_data. That's not a kernel
> issue.
>
> For cases like addr/len etc validation, it should be sound. I'll double
> check this in the morning as well, and obviously would need to be folded
> in along the way.
>
> I'd appreciate your opinion on this part, if you see any major issues
> with it, or if I missed something.

The io_sqe_needs_user() checks still look racy. If that helper sees a
IORING_OP_READ_FIXED, but then __io_submit_sqe() sees a
IORING_OP_READV - especially if this happens in io_sq_wq_submit_work()
-, I think you could potentially end up in places like
io_import_iovec() without having done the set_fs(USER_DS) and
use_mm(), causing the access to potentially occur with KERNEL_DS and a
lazy mm.

WARNING: multiple messages have this Message-ID (diff)
From: Jann Horn <jannh@google.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-aio@kvack.org, linux-block@vger.kernel.org,
	linux-man <linux-man@vger.kernel.org>,
	Linux API <linux-api@vger.kernel.org>,
	hch@lst.de, jmoyer@redhat.com, Avi Kivity <avi@scylladb.com>
Subject: Re: [PATCH 05/18] Add io_uring IO interface
Date: Tue, 29 Jan 2019 16:56:31 +0100	[thread overview]
Message-ID: <CAG48ez0sNBjgW7ynpNC+sir-_AuccY1sKguiD+VAXvL9-j4iag@mail.gmail.com> (raw)
In-Reply-To: <b5902860-30a9-3dc9-b513-3d892afdc51b@kernel.dk>

On Tue, Jan 29, 2019 at 4:46 AM Jens Axboe <axboe@kernel.dk> wrote:
> On 1/28/19 7:21 PM, Jann Horn wrote:
> > Please create a local copy of the request before parsing it to keep
> > the data from changing under you. Additionally, it might make sense to
> > annotate every pointer to shared memory with a comment, or something
> > like that, to ensure that anyone looking at the code can immediately
> > see for which pointers special caution is required on access.
>
> I took a look at the viability of NOT having to local copy the data, and
> I don't think it's too bad. Local copy has a noticeable impact on the
> performance, hence I'd really (REALLY) like to avoid it.
>
> Here's something on top of the current git branch. I think I even went a
> bit too far in some areas, but it should hopefully catch the cases where
> we might end up double evaluating the parts of the sqe that we depend
> on. For most of the sqe reading we don't really care too much. For
> instance, the sqe->user_data. If the app changes this field, then it
> just gets whatever passed back in cqe->user_data. That's not a kernel
> issue.
>
> For cases like addr/len etc validation, it should be sound. I'll double
> check this in the morning as well, and obviously would need to be folded
> in along the way.
>
> I'd appreciate your opinion on this part, if you see any major issues
> with it, or if I missed something.

The io_sqe_needs_user() checks still look racy. If that helper sees a
IORING_OP_READ_FIXED, but then __io_submit_sqe() sees a
IORING_OP_READV - especially if this happens in io_sq_wq_submit_work()
-, I think you could potentially end up in places like
io_import_iovec() without having done the set_fs(USER_DS) and
use_mm(), causing the access to potentially occur with KERNEL_DS and a
lazy mm.

--
To unsubscribe, send a message with 'unsubscribe linux-aio' in
the body to majordomo@kvack.org.  For more info on Linux AIO,
see: http://www.kvack.org/aio/
Don't email: <a href=mailto:"aart@kvack.org">aart@kvack.org</a>

  reply	other threads:[~2019-01-29 15:56 UTC|newest]

Thread overview: 201+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-28 21:35 [PATCHSET v8] io_uring IO interface Jens Axboe
2019-01-28 21:35 ` Jens Axboe
2019-01-28 21:35 ` [PATCH 01/18] fs: add an iopoll method to struct file_operations Jens Axboe
2019-01-28 21:35   ` Jens Axboe
2019-01-28 21:35 ` [PATCH 02/18] block: wire up block device iopoll method Jens Axboe
2019-01-28 21:35   ` Jens Axboe
2019-01-28 21:35 ` [PATCH 03/18] block: add bio_set_polled() helper Jens Axboe
2019-01-28 21:35   ` Jens Axboe
2019-01-28 21:35 ` [PATCH 04/18] iomap: wire up the iopoll method Jens Axboe
2019-01-28 21:35   ` Jens Axboe
2019-01-28 21:35 ` [PATCH 05/18] Add io_uring IO interface Jens Axboe
2019-01-28 21:35   ` Jens Axboe
2019-01-28 21:53   ` Jeff Moyer
2019-01-28 21:53     ` Jeff Moyer
2019-01-28 21:56     ` Jens Axboe
2019-01-28 21:56       ` Jens Axboe
2019-01-28 22:32   ` Jann Horn
2019-01-28 22:32     ` Jann Horn
2019-01-28 23:46     ` Jens Axboe
2019-01-28 23:46       ` Jens Axboe
2019-01-28 23:59       ` Jann Horn
2019-01-28 23:59         ` Jann Horn
2019-01-29  0:03         ` Jens Axboe
2019-01-29  0:03           ` Jens Axboe
2019-01-29  0:31           ` Jens Axboe
2019-01-29  0:31             ` Jens Axboe
2019-01-29  0:34             ` Jann Horn
2019-01-29  0:34               ` Jann Horn
2019-01-29  0:55               ` Jens Axboe
2019-01-29  0:55                 ` Jens Axboe
2019-01-29  0:58                 ` Jann Horn
2019-01-29  0:58                   ` Jann Horn
2019-01-29  1:01                   ` Jens Axboe
2019-01-29  1:01                     ` Jens Axboe
2019-02-01 16:57         ` Matt Mullins
2019-02-01 16:57           ` Matt Mullins
2019-02-01 17:04           ` Jann Horn
2019-02-01 17:04             ` Jann Horn
2019-02-01 17:23             ` Jann Horn
2019-02-01 17:23               ` Jann Horn
2019-02-01 18:05               ` Al Viro
2019-02-01 18:05                 ` Al Viro
2019-01-29  1:07   ` Jann Horn
2019-01-29  1:07     ` Jann Horn
2019-01-29  2:21     ` Jann Horn
2019-01-29  2:21       ` Jann Horn
2019-01-29  2:54       ` Jens Axboe
2019-01-29  2:54         ` Jens Axboe
2019-01-29  3:46       ` Jens Axboe
2019-01-29  3:46         ` Jens Axboe
2019-01-29 15:56         ` Jann Horn [this message]
2019-01-29 15:56           ` Jann Horn
2019-01-29 16:06           ` Jens Axboe
2019-01-29 16:06             ` Jens Axboe
2019-01-29  2:21     ` Jens Axboe
2019-01-29  2:21       ` Jens Axboe
2019-01-29  1:29   ` Jann Horn
2019-01-29  1:29     ` Jann Horn
2019-01-29  1:31     ` Jens Axboe
2019-01-29  1:31       ` Jens Axboe
2019-01-29  1:32       ` Jann Horn
2019-01-29  1:32         ` Jann Horn
2019-01-29  2:23         ` Jens Axboe
2019-01-29  2:23           ` Jens Axboe
2019-01-29  7:12   ` Bert Wesarg
2019-01-29  7:12     ` Bert Wesarg
2019-01-29 12:12   ` Florian Weimer
2019-01-29 12:12     ` Florian Weimer
2019-01-29 13:35     ` Jens Axboe
2019-01-29 13:35       ` Jens Axboe
2019-01-29 15:38       ` Jann Horn
2019-01-29 15:38         ` Jann Horn
2019-01-29 15:54         ` Jens Axboe
2019-01-29 15:54           ` Jens Axboe
2019-01-29 16:55         ` Christoph Hellwig
2019-01-29 16:55           ` Christoph Hellwig
2019-01-29 15:35   ` Jann Horn
2019-01-29 15:35     ` Jann Horn
2019-01-29 15:39     ` Jens Axboe
2019-01-29 15:39       ` Jens Axboe
2019-01-28 21:35 ` [PATCH 06/18] io_uring: add fsync support Jens Axboe
2019-01-28 21:35   ` Jens Axboe
2019-01-28 21:35 ` [PATCH 07/18] io_uring: support for IO polling Jens Axboe
2019-01-28 21:35   ` Jens Axboe
2019-01-29 17:24   ` Christoph Hellwig
2019-01-29 17:24     ` Christoph Hellwig
2019-01-29 18:31     ` Jens Axboe
2019-01-29 18:31       ` Jens Axboe
2019-01-29 19:10       ` Jens Axboe
2019-01-29 19:10         ` Jens Axboe
2019-01-29 20:35         ` Jeff Moyer
2019-01-29 20:35           ` Jeff Moyer
2019-01-29 20:37           ` Jens Axboe
2019-01-29 20:37             ` Jens Axboe
2019-01-28 21:35 ` [PATCH 08/18] fs: add fget_many() and fput_many() Jens Axboe
2019-01-28 21:35   ` Jens Axboe
2019-01-28 21:35 ` [PATCH 09/18] io_uring: use fget/fput_many() for file references Jens Axboe
2019-01-28 21:35   ` Jens Axboe
2019-01-28 21:56   ` Jann Horn
2019-01-28 21:56     ` Jann Horn
2019-01-28 22:03     ` Jens Axboe
2019-01-28 22:03       ` Jens Axboe
2019-01-28 21:35 ` [PATCH 10/18] io_uring: batch io_kiocb allocation Jens Axboe
2019-01-28 21:35   ` Jens Axboe
2019-01-29 17:26   ` Christoph Hellwig
2019-01-29 17:26     ` Christoph Hellwig
2019-01-29 18:14     ` Jens Axboe
2019-01-29 18:14       ` Jens Axboe
2019-01-28 21:35 ` [PATCH 11/18] block: implement bio helper to add iter bvec pages to bio Jens Axboe
2019-01-28 21:35   ` Jens Axboe
2019-01-28 21:35 ` [PATCH 12/18] io_uring: add support for pre-mapped user IO buffers Jens Axboe
2019-01-28 21:35   ` Jens Axboe
2019-01-28 23:35   ` Jann Horn
2019-01-28 23:35     ` Jann Horn
2019-01-28 23:50     ` Jens Axboe
2019-01-28 23:50       ` Jens Axboe
2019-01-29  0:36       ` Jann Horn
2019-01-29  0:36         ` Jann Horn
2019-01-29  1:25         ` Jens Axboe
2019-01-29  1:25           ` Jens Axboe
2019-01-28 21:35 ` [PATCH 13/18] io_uring: add file set registration Jens Axboe
2019-01-28 21:35   ` Jens Axboe
2019-01-29 16:36   ` Jann Horn
2019-01-29 16:36     ` Jann Horn
2019-01-29 18:13     ` Jens Axboe
2019-01-29 18:13       ` Jens Axboe
2019-01-28 21:35 ` [PATCH 14/18] io_uring: add submission polling Jens Axboe
2019-01-28 21:35   ` Jens Axboe
2019-01-28 21:35 ` [PATCH 15/18] io_uring: add io_kiocb ref count Jens Axboe
2019-01-28 21:35   ` Jens Axboe
2019-01-29 17:26   ` Christoph Hellwig
2019-01-29 17:26     ` Christoph Hellwig
2019-01-28 21:35 ` [PATCH 16/18] io_uring: add support for IORING_OP_POLL Jens Axboe
2019-01-28 21:35   ` Jens Axboe
2019-01-28 21:35 ` [PATCH 17/18] io_uring: allow workqueue item to handle multiple buffered requests Jens Axboe
2019-01-28 21:35   ` Jens Axboe
2019-01-28 21:35 ` [PATCH 18/18] io_uring: add io_uring_event cache hit information Jens Axboe
2019-01-28 21:35   ` Jens Axboe
  -- strict thread matches above, loose matches on Subject: below --
2019-02-07 19:55 [PATCHSET v12] io_uring IO interface Jens Axboe
2019-02-07 19:55 ` [PATCH 05/18] Add " Jens Axboe
2019-02-07 19:55   ` Jens Axboe
2019-02-07 20:15   ` Keith Busch
2019-02-07 20:15     ` Keith Busch
2019-02-07 20:16     ` Jens Axboe
2019-02-07 20:16       ` Jens Axboe
2019-02-01 15:23 [PATCHSET v11] " Jens Axboe
2019-02-01 15:24 ` [PATCH 05/18] Add " Jens Axboe
2019-02-01 15:24   ` Jens Axboe
2019-02-01 18:20   ` Florian Weimer
2019-02-01 18:20     ` Florian Weimer
2019-02-05 16:58     ` Jens Axboe
2019-02-05 16:58       ` Jens Axboe
2019-02-04 23:22   ` Jeff Moyer
2019-02-04 23:22     ` Jeff Moyer
2019-02-04 23:52     ` Jeff Moyer
2019-02-04 23:52       ` Jeff Moyer
2019-02-05 16:59       ` Jens Axboe
2019-02-05 16:59         ` Jens Axboe
2019-02-05 16:58     ` Jens Axboe
2019-02-05 16:58       ` Jens Axboe
2019-01-30 21:55 [PATCHSET v10] " Jens Axboe
2019-01-30 21:55 ` [PATCH 05/18] Add " Jens Axboe
2019-01-30 21:55   ` Jens Axboe
2019-01-29 19:26 [PATCHSET v9] " Jens Axboe
2019-01-29 19:26 ` [PATCH 05/18] Add " Jens Axboe
2019-01-29 19:26   ` Jens Axboe
2019-01-23 15:35 [PATCHSET v7] " Jens Axboe
2019-01-23 15:35 ` [PATCH 05/18] Add " Jens Axboe
2019-01-28 14:57   ` Christoph Hellwig
2019-01-28 14:57     ` Christoph Hellwig
2019-01-28 16:26     ` Jens Axboe
2019-01-28 16:26       ` Jens Axboe
2019-01-28 16:34       ` Christoph Hellwig
2019-01-28 16:34         ` Christoph Hellwig
2019-01-28 19:32         ` Jens Axboe
2019-01-28 19:32           ` Jens Axboe
2019-01-28 18:25     ` Jens Axboe
2019-01-28 18:25       ` Jens Axboe
2019-01-29  6:30       ` Christoph Hellwig
2019-01-29  6:30         ` Christoph Hellwig
2019-01-29 11:58         ` Arnd Bergmann
2019-01-29 11:58           ` Arnd Bergmann
2019-01-29 15:20           ` Jens Axboe
2019-01-29 15:20             ` Jens Axboe
2019-01-29 16:18             ` Arnd Bergmann
2019-01-29 16:18               ` Arnd Bergmann
2019-01-29 16:19               ` Jens Axboe
2019-01-29 16:19                 ` Jens Axboe
2019-01-29 16:26                 ` Arnd Bergmann
2019-01-29 16:26                   ` Arnd Bergmann
2019-01-29 16:28                   ` Jens Axboe
2019-01-29 16:28                     ` Jens Axboe
2019-01-29 16:46                     ` Arnd Bergmann
2019-01-29 16:46                       ` Arnd Bergmann
2019-01-29  0:47     ` Andy Lutomirski
2019-01-29  0:47       ` Andy Lutomirski
2019-01-29  1:20       ` Jens Axboe
2019-01-29  1:20         ` Jens Axboe
2019-01-29  6:45         ` Christoph Hellwig
2019-01-29  6:45           ` Christoph Hellwig
2019-01-29 12:05           ` Arnd Bergmann
2019-01-29 12:05             ` Arnd Bergmann
2019-01-31  5:11         ` Andy Lutomirski
2019-01-31  5:11           ` Andy Lutomirski
2019-01-31 16:37           ` Jens Axboe
2019-01-31 16:37             ` Jens Axboe

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=CAG48ez0sNBjgW7ynpNC+sir-_AuccY1sKguiD+VAXvL9-j4iag@mail.gmail.com \
    --to=jannh@google.com \
    --cc=avi@scylladb.com \
    --cc=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=jmoyer@redhat.com \
    --cc=linux-aio@kvack.org \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-man@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.