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]>
Subject: [GIT PULL] io_uring fixes for 5.11-rc4
Date: Sat, 16 Jan 2021 11:02:58 -0700	[thread overview]
Message-ID: <[email protected]> (raw)

Hi Linus,

We still have a pending fix for a cancelation issue, but it's still
being investigated and the plan is for that to hit 5.11-rc5. Changes in
this pull request:

- Dead mm handling fix (Pavel)

- SQPOLL setup error handling (Pavel)

- Flush timeout sequence fix (Marcelo)

- Missing finish_wait() for one exit case

Please pull!


The following changes since commit d9d05217cb6990b9a56e13b56e7a1b71e2551f6c:

  io_uring: stop SQPOLL submit on creator's death (2021-01-09 09:21:43 -0700)

are available in the Git repository at:

  git://git.kernel.dk/linux-block.git tags/io_uring-5.11-2021-01-16

for you to fetch changes up to a8d13dbccb137c46fead2ec1a4f1fbc8cfc9ea91:

  io_uring: ensure finish_wait() is always called in __io_uring_task_cancel() (2021-01-15 16:04:23 -0700)

----------------------------------------------------------------
io_uring-5.11-2021-01-16

----------------------------------------------------------------
Jens Axboe (1):
      io_uring: ensure finish_wait() is always called in __io_uring_task_cancel()

Marcelo Diop-Gonzalez (1):
      io_uring: flush timeouts that should already have expired

Pavel Begunkov (4):
      io_uring: drop mm and files after task_work_run
      io_uring: don't take files/mm for a dead task
      io_uring: fix null-deref in io_disable_sqo_submit
      io_uring: do sqo disable on install_fd error

 fs/io_uring.c | 46 +++++++++++++++++++++++++++++++++++++++++-----
 1 file changed, 41 insertions(+), 5 deletions(-)

-- 
Jens Axboe


             reply	other threads:[~2021-01-16 18:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-16 18:02 Jens Axboe [this message]
2021-01-16 20:02 ` [GIT PULL] io_uring fixes for 5.11-rc4 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