public inbox for [email protected]
 help / color / mirror / Atom feed
From: Jens Axboe <[email protected]>
To: [email protected]
Cc: [email protected]
Subject: [GIT PULL] Followup io_uring fixes for 5.12-rc
Date: Thu, 25 Feb 2021 15:27:00 -0700	[thread overview]
Message-ID: <[email protected]> (raw)

Hi Linus,

A collection of later fixes that we should get into this release:

- Series of submission cleanups (Pavel)

- A few fixes for issues from earlier this merge window (Pavel, me)

- IOPOLL resubmission fix

- task_work locking fix (Hao)

Please pull!


The following changes since commit 0b81e80c813f92520667c872d499a2dba8377be6:

  io_uring: tctx->task_lock should be IRQ safe (2021-02-16 11:11:20 -0700)

are available in the Git repository at:

  git://git.kernel.dk/linux-block.git tags/for-5.12/io_uring-2021-02-25

for you to fetch changes up to cb5e1b81304e089ee3ca948db4d29f71902eb575:

  Revert "io_uring: wait potential ->release() on resurrect" (2021-02-25 07:37:35 -0700)

----------------------------------------------------------------
for-5.12/io_uring-2021-02-25

----------------------------------------------------------------
Hao Xu (1):
      io_uring: don't hold uring_lock when calling io_run_task_work*

Jens Axboe (3):
      io_uring: make the !CONFIG_NET helpers a bit more robust
      io_uring: don't attempt IO reissue from the ring exit path
      Revert "io_uring: wait potential ->release() on resurrect"

Pavel Begunkov (21):
      io_uring: fix read memory leak
      io_uring: kill fictitious submit iteration index
      io_uring: keep io_*_prep() naming consistent
      io_uring: don't duplicate ->file check in sfr
      io_uring: move io_init_req()'s definition
      io_uring: move io_init_req() into io_submit_sqe()
      io_uring: move req link into submit_state
      io_uring: don't submit link on error
      io_uring: split sqe-prep and async setup
      io_uring: do io_*_prep() early in io_submit_sqe()
      io_uring: don't do async setup for links' heads
      io_uring: fail links more in io_submit_sqe()
      io_uring: don't take uring_lock during iowq cancel
      io_uring: fail io-wq submission from a task_work
      io_uring: zero ref_node after killing it
      io_uring: keep generic rsrc infra generic
      io_uring: wait potential ->release() on resurrect
      io_uring: fix leaving invalid req->flags
      io_uring: run task_work on io_uring_register()
      io_uring: clear request count when freeing caches
      io_uring: fix locked_free_list caches_free()

 fs/io_uring.c | 686 +++++++++++++++++++++++++++++-----------------------------
 1 file changed, 346 insertions(+), 340 deletions(-)

-- 
Jens Axboe


             reply	other threads:[~2021-02-25 22:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-25 22:27 Jens Axboe [this message]
2021-02-26 18:16 ` [GIT PULL] Followup io_uring fixes for 5.12-rc Linus Torvalds
2021-02-26 18:21   ` Jens Axboe
2021-02-26 22:23 ` 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] \
    /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