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.8-rc5
Date: Fri, 10 Jul 2020 10:01:20 -0600	[thread overview]
Message-ID: <[email protected]> (raw)

Hi Linus,

- Fix memleak for error path in registered files (Yang)
- Export CQ overflow state in flags, necessary to fix a case where
  liburing doesn't know if it needs to enter the kernel (Xiaoguang)
- Fix for a regression in when user memory is accounted freed, causing
  issues with back-to-back ring exit + init if the ulimit -l setting is
  very tight.

Please pull!


The following changes since commit b7db41c9e03b5189bc94993bd50e4506ac9e34c1:

  io_uring: fix regression with always ignoring signals in io_cqring_wait() (2020-07-04 13:44:45 -0600)

are available in the Git repository at:

  git://git.kernel.dk/linux-block.git tags/io_uring-5.8-2020-07-10

for you to fetch changes up to 309fc03a3284af62eb6082fb60327045a1dabf57:

  io_uring: account user memory freed when exit has been queued (2020-07-10 09:18:35 -0600)

----------------------------------------------------------------
io_uring-5.8-2020-07-10

----------------------------------------------------------------
Jens Axboe (1):
      io_uring: account user memory freed when exit has been queued

Xiaoguang Wang (1):
      io_uring: export cq overflow status to userspace

Yang Yingliang (2):
      io_uring: fix memleak in __io_sqe_files_update()
      io_uring: fix memleak in io_sqe_files_register()

 fs/io_uring.c                 | 29 +++++++++++++++++++++++------
 include/uapi/linux/io_uring.h |  1 +
 2 files changed, 24 insertions(+), 6 deletions(-)

-- 
Jens Axboe


             reply	other threads:[~2020-07-10 16:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-10 16:01 Jens Axboe [this message]
2020-07-10 17:05 ` [GIT PULL] io_uring fixes for 5.8-rc5 pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2020-07-12 16:30 Jens Axboe
2020-07-12 19:30 ` 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