public inbox for [email protected]
 help / color / mirror / Atom feed
From: Jens Axboe <[email protected]>
To: Linus Torvalds <[email protected]>
Cc: io-uring <[email protected]>,
	"[email protected]" <[email protected]>
Subject: [GIT PULL] io_uring fixes for 5.5-rc7
Date: Fri, 17 Jan 2020 07:33:15 -0700	[thread overview]
Message-ID: <[email protected]> (raw)

Hi Linus,

A set of fixes that should go into this release. This pull request
contains:

- Ensure ->result is always set when IO is retried (Bijan)

- In conjunction with the above, fix a regression in polled IO issue
  when retried (me/Bijan)

- Don't setup async context for read/write fixed, otherwise we may
  wrongly map the iovec on retry (me)

- Cancel io-wq work if we fail getting mm reference (me)

- Ensure dependent work is always initialized correctly (me)

- Only allow original task to submit IO, don't allow it from a passed
  ring fd (me)

Please pull!


  git://git.kernel.dk/linux-block.git tags/io_uring-5.5-2020-01-16


----------------------------------------------------------------
Bijan Mottahedeh (1):
      io_uring: clear req->result always before issuing a read/write request

Jens Axboe (5):
      io_uring: don't setup async context for read/write fixed
      io-wq: cancel work if we fail getting a mm reference
      io_uring: be consistent in assigning next work from handler
      io_uring: ensure workqueue offload grabs ring mutex for poll list
      io_uring: only allow submit from owning task

 fs/io-wq.c    | 12 ++++++----
 fs/io_uring.c | 72 +++++++++++++++++++++++++++++++++++++++--------------------
 2 files changed, 56 insertions(+), 28 deletions(-)

-- 
Jens Axboe


             reply	other threads:[~2020-01-17 14:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-17 14:33 Jens Axboe [this message]
2020-01-17 20:00 ` [GIT PULL] io_uring fixes for 5.5-rc7 pr-tracker-bot

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] \
    [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