io-uring.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: io-uring <io-uring@vger.kernel.org>
Subject: [GIT PULL] io_uring fixes for 5.5-rc4
Date: Thu, 26 Dec 2019 11:21:51 -0700	[thread overview]
Message-ID: <69cdbfdc-da7d-a3fe-f196-3c0819757908@kernel.dk> (raw)

Hi Linus,

This pull request:

- Removal of now unused busy wqe list (Hillf)

- Add cond_resched() to io-wq work processing (Hillf)

- And then the series that I hinted at from last week, which removes the
  sqe from the io_kiocb and keeps all sqe handling on the prep side.
  This guarantees that an opcode can't do the wrong thing and read the
  sqe more than once. This is unchanged from last week, no issues have
  been observed with this in testing. Hence I really think we should
  fold this into 5.5.

Please pull!


  git://git.kernel.dk/linux-block.git tags/io_uring-5.5-20191226


----------------------------------------------------------------
Hillf Danton (2):
      io-wq: remove unused busy list from io_sqe
      io-wq: add cond_resched() to worker thread

Jens Axboe (7):
      io_uring: use u64_to_user_ptr() consistently
      io_uring: add and use struct io_rw for read/writes
      io_uring: move all prep state for IORING_OP_CONNECT to prep handler
      io_uring: move all prep state for IORING_OP_{SEND,RECV}_MGS to prep handler
      io_uring: read 'count' for IORING_OP_TIMEOUT in prep handler
      io_uring: standardize the prep methods
      io_uring: pass in 'sqe' to the prep handlers

 fs/io-wq.c    |  10 +-
 fs/io_uring.c | 690 ++++++++++++++++++++++++++++++----------------------------
 2 files changed, 357 insertions(+), 343 deletions(-)

-- 
Jens Axboe


                 reply	other threads:[~2019-12-26 18:21 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=69cdbfdc-da7d-a3fe-f196-3c0819757908@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=io-uring@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).