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.14-rc3
Date: Sat, 24 Jul 2021 09:53:15 -0600	[thread overview]
Message-ID: <[email protected]> (raw)

Hi Linus,

A few io_uring fixes that should go into 5.14-rc3:

- Fix a memory leak due to a race condition in io_init_wq_offload (Yang)

- Poll error handling fixes (Pavel)

- Fix early fdput() regression (me)

- Don't reissue iopoll requests off release path (me)

- Add a safety check for io-wq queue off wrong path (me)

Please pull!


The following changes since commit 1b48773f9fd09f311d1166ce1dd50652ebe05218:

  io_uring: fix io_drain_req() (2021-07-11 16:39:06 -0600)

are available in the Git repository at:

  git://git.kernel.dk/linux-block.git tags/io_uring-5.14-2021-07-24

for you to fetch changes up to 991468dcf198bb87f24da330676724a704912b47:

  io_uring: explicitly catch any illegal async queue attempt (2021-07-23 16:44:51 -0600)

----------------------------------------------------------------
io_uring-5.14-2021-07-24

----------------------------------------------------------------
Jens Axboe (3):
      io_uring: fix early fdput() of file
      io_uring: never attempt iopoll reissue from release path
      io_uring: explicitly catch any illegal async queue attempt

Pavel Begunkov (2):
      io_uring: explicitly count entries for poll reqs
      io_uring: remove double poll entry on arm failure

Yang Yingliang (1):
      io_uring: fix memleak in io_init_wq_offload()

 fs/io-wq.c    |  7 ++++++-
 fs/io_uring.c | 55 +++++++++++++++++++++++++++++++++++++++----------------
 2 files changed, 45 insertions(+), 17 deletions(-)

-- 
Jens Axboe


             reply	other threads:[~2021-07-24 15:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-24 15:53 Jens Axboe [this message]
2021-07-24 20:16 ` [GIT PULL] io_uring fixes for 5.14-rc3 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