From: Jens Axboe <[email protected]>
To: Linus Torvalds <[email protected]>
Cc: io-uring <[email protected]>
Subject: Re: [GIT PULL] io_uring fixes for 6.0-rc1
Date: Thu, 11 Aug 2022 08:35:32 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 8/10/22 7:01 PM, Jens Axboe wrote:
> 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!
Of course a few more things came in right after sending this one. Just
disregard this pull request, will send another one in a day or two.
Thanks!
--
Jens Axboe
next prev parent reply other threads:[~2022-08-11 14:35 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-11 1:01 [GIT PULL] io_uring fixes for 6.0-rc1 Jens Axboe
2022-08-11 14:35 ` Jens Axboe [this message]
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