From: Jens Axboe <[email protected]>
To: Pavel Begunkov <[email protected]>, [email protected]
Subject: Re: [PATCH 0/4] iov remapping hardening
Date: Sat, 5 Sep 2020 16:51:56 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 9/5/20 4:34 PM, Jens Axboe wrote:
> On 9/5/20 4:15 PM, Pavel Begunkov wrote:
>> On 06/09/2020 00:58, Jens Axboe wrote:
>>> On 9/5/20 3:45 PM, Pavel Begunkov wrote:
>>>> This cleans bits around iov remapping. The patches were initially
>>>> for-5.9, but if you want it for 5.10 let me know, I'll rebase.
>>>
>>> Yeah let's aim these for 5.10 - look fine to me, but would rather avoid
>>> any extra churn if at all possible.
>>
>> These applies cleanly for-5.10/io_uring. It should conflict with
>
> Great, I'll queue them up then.
>
>> yours req->io shrinking patches, but it seems you haven't queued
>> them yet.
>
> Which ones?
Ah yes, totally forgot to queue that... Doesn't matter with the conflicts,
some of the others caused an issue or two as well. I've queued it for
testing.
Thanks for the reminder :-)
--
Jens Axboe
prev parent reply other threads:[~2020-09-05 22:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-05 21:45 [PATCH 0/4] iov remapping hardening Pavel Begunkov
2020-09-05 21:45 ` [PATCH 1/4] io_uring: simplify io_rw_prep_async() Pavel Begunkov
2020-09-05 21:45 ` [PATCH 2/4] io_uring: refactor io_req_map_rw() Pavel Begunkov
2020-09-05 21:45 ` [PATCH 3/4] io_uring: fix ovelapped memcpy in io_req_map_rw() Pavel Begunkov
2020-09-05 21:45 ` [PATCH 4/4] io_uring: kill extra user_bufs check Pavel Begunkov
2020-09-05 21:58 ` [PATCH 0/4] iov remapping hardening Jens Axboe
2020-09-05 22:15 ` Pavel Begunkov
2020-09-05 22:34 ` Jens Axboe
2020-09-05 22:51 ` Jens Axboe [this message]
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