From: Jens Axboe <[email protected]>
To: Linus Torvalds <[email protected]>
Cc: io-uring <[email protected]>
Subject: [GIT PULL] io_uring fixes for 6.0-rc1
Date: Wed, 10 Aug 2022 19:01:18 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
Hi Linus,
A few fixes that should go upstream before 6.0-rc1. In detail:
- Regression fix for this merge window, fixing a wrong order of
arguments for io_req_set_res() for passthru (Dylan)
- Fix for the audit code leaking context memory (Peilin)
- Ensure that provided buffers are memcg accounted (Pavel)
- Correctly handle short zero-copy sends (Pavel)
- Sparse warning fixes for the recvmsg multishot command (Dylan)
Please pull!
The following changes since commit e2b542100719a93f8cdf6d90185410d38a57a4c1:
Merge tag 'flexible-array-transformations-UAPI-6.0-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gustavoars/linux (2022-08-02 19:50:47 -0700)
are available in the Git repository at:
git://git.kernel.dk/linux-block.git tags/io_uring-6.0-2022-08-10
for you to fetch changes up to d1f6222c4978817712e0f2825ce9e830763f0695:
io_uring: fix io_recvmsg_prep_multishot sparse warnings (2022-08-05 08:41:18 -0600)
----------------------------------------------------------------
io_uring-6.0-2022-08-10
----------------------------------------------------------------
Dylan Yudaken (1):
io_uring: fix io_recvmsg_prep_multishot sparse warnings
Ming Lei (1):
io_uring: pass correct parameters to io_req_set_res
Pavel Begunkov (2):
io_uring: mem-account pbuf buckets
io_uring/net: send retry for zerocopy
Peilin Ye (1):
audit, io_uring, io-wq: Fix memory leak in io_sq_thread() and io_wqe_worker()
include/linux/audit.h | 5 -----
io_uring/io-wq.c | 3 ---
io_uring/kbuf.c | 2 +-
io_uring/net.c | 24 +++++++++++++++++++-----
io_uring/sqpoll.c | 4 ----
io_uring/uring_cmd.c | 2 +-
kernel/auditsc.c | 25 -------------------------
7 files changed, 21 insertions(+), 44 deletions(-)
--
Jens Axboe
next reply other threads:[~2022-08-11 1:01 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-11 1:01 Jens Axboe [this message]
2022-08-11 14:35 ` [GIT PULL] io_uring fixes for 6.0-rc1 Jens Axboe
2022-08-13 21:48 ` pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2022-08-12 12:46 Jens Axboe
2022-08-12 20:28 ` Linus Torvalds
2022-08-12 20:44 ` Jens Axboe
2022-08-12 21:01 ` Jens Axboe
2022-08-12 21:08 ` Jens Axboe
2022-08-12 21:34 ` Jens Axboe
2022-08-12 21:43 ` Linus Torvalds
2022-08-12 21:53 ` Jens Axboe
2022-08-12 21:54 ` Linus Torvalds
2022-08-12 22:01 ` Linus Torvalds
2022-08-12 22:16 ` Jens Axboe
2022-08-12 22:11 ` Jens Axboe
2022-08-12 22:19 ` Jens Axboe
2022-08-12 22:23 ` Keith Busch
2022-08-12 22:25 ` Jens Axboe
2022-08-12 22:27 ` Jens Axboe
2022-08-12 22:35 ` Linus Torvalds
2022-08-12 22:38 ` Jens Axboe
2022-08-12 22:52 ` Linus Torvalds
2022-08-12 22:55 ` Jens Axboe
2022-08-12 21:37 ` Linus Torvalds
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