All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: io-uring <io-uring@vger.kernel.org>
Subject: [GIT PULL] io_uring fixes for 5.17-rc6
Date: Thu, 24 Feb 2022 10:30:19 -0700	[thread overview]
Message-ID: <16541e0b-e3ce-9e7f-4baa-20cd6e37db1b@kernel.dk> (raw)

Hi Linus,

A few minor fixes for 5.17-rc6:

- Add a conditional schedule point in io_add_buffers() (Eric)

- Fix for a quiesce speedup merged in this release (Dylan)

- Don't convert to jiffies for event timeout waiting, it's way too
  coarse when we accept a timespec as input (me)

Please pull!


The following changes since commit 0a3f1e0beacf6cc8ae5f846b0641c1df476e83d6:

  mm: io_uring: allow oom-killer from io_uring_setup (2022-02-07 08:44:01 -0700)

are available in the Git repository at:

  git://git.kernel.dk/linux-block.git tags/io_uring-5.17-2022-02-23

for you to fetch changes up to 80912cef18f16f8fe59d1fb9548d4364342be360:

  io_uring: disallow modification of rsrc_data during quiesce (2022-02-22 09:57:32 -0700)

----------------------------------------------------------------
io_uring-5.17-2022-02-23

----------------------------------------------------------------
Dylan Yudaken (1):
      io_uring: disallow modification of rsrc_data during quiesce

Eric Dumazet (1):
      io_uring: add a schedule point in io_add_buffers()

Jens Axboe (1):
      io_uring: don't convert to jiffies for waiting on timeouts

 fs/io_uring.c | 24 +++++++++++++++++-------
 1 file changed, 17 insertions(+), 7 deletions(-)

-- 
Jens Axboe


             reply	other threads:[~2022-02-24 17:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-24 17:30 Jens Axboe [this message]
2022-02-24 19:18 ` [GIT PULL] io_uring fixes for 5.17-rc6 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 \
    --in-reply-to=16541e0b-e3ce-9e7f-4baa-20cd6e37db1b@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=io-uring@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.