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 6.10-rc2
Date: Fri, 31 May 2024 08:29:50 -0600	[thread overview]
Message-ID: <[email protected]> (raw)

Hi Linus,

A couple of minor fixes for issues introduced in the 6.10 merge window:

- Ensure that all read/write ops have an appropriate cleanup handler set
  (Breno)

- Regression for applications still doing multiple mmaps even if
  FEAT_SINGLE_MMAP is set (me)

- Move kmsg inquiry setting above any potential failure point, avoiding
  a spurious NONEMPTY flag setting on early error (me)

Please pull!


The following changes since commit 1613e604df0cd359cf2a7fbd9be7a0bcfacfabd0:

  Linux 6.10-rc1 (2024-05-26 15:20:12 -0700)

are available in the Git repository at:

  git://git.kernel.dk/linux.git tags/io_uring-6.10-20240530

for you to fetch changes up to 18414a4a2eabb0281d12d374c92874327e0e3fe3:

  io_uring/net: assign kmsg inq/flags before buffer selection (2024-05-30 14:04:37 -0600)

----------------------------------------------------------------
io_uring-6.10-20240530

----------------------------------------------------------------
Breno Leitao (1):
      io_uring/rw: Free iovec before cleaning async data

Jens Axboe (2):
      io_uring: don't attempt to mmap larger than what the user asks for
      io_uring/net: assign kmsg inq/flags before buffer selection

 io_uring/memmap.c | 5 +++--
 io_uring/net.c    | 6 +++---
 io_uring/opdef.c  | 5 +++++
 3 files changed, 11 insertions(+), 5 deletions(-)

-- 
Jens Axboe


             reply	other threads:[~2024-05-31 14:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-31 14:29 Jens Axboe [this message]
2024-05-31 23:40 ` [GIT PULL] io_uring fixes for 6.10-rc2 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