From: Jens Axboe <axboe@kernel.dk>
To: Sasha Levin <sashal@kernel.org>
Cc: stable@vger.kernel.org
Subject: Re: io_uring stable 5.3 backports
Date: Sun, 27 Oct 2019 06:01:03 -0600 [thread overview]
Message-ID: <f90a0bd3-3074-ee14-dea9-63d520bd72a2@kernel.dk> (raw)
In-Reply-To: <20191027085204.GA1560@sasha-vm>
On 10/27/19 2:52 AM, Sasha Levin wrote:
> On Sat, Oct 26, 2019 at 05:33:41PM -0600, Jens Axboe wrote:
>> Hi,
>>
>> For some reason I forgot to mark these stable, but they should go
>> into stable. In order of applying them, they are:
>>
>> bc808bced39f4e4b626c5ea8c63d5e41fce7205a
>
> This commit says it fixes c576666863b78 ("io_uring: optimize
> submit_and_wait API") which is not in the stable tree.
>
>> ef03681ae8df770745978148a7fb84796ae99cba
>
> This commit doesn't say so, but really it fixes 5262f567987d3
> ("io_uring: IORING_OP_TIMEOUT support") which is not in the stable tree.
>
>> a1f58ba46f794b1168d1107befcf3d4b9f9fd453
>
> Same as the commit above.
Oh man, sorry about that, I always forget to check if all of them are in
5.3. I blame the fact that I backport everything to our internal tree,
which is 5.2 based. But yes, you are of course right, those three can be
dropped.
>> 84d55dc5b9e57b513a702fbc358e1b5489651590
>> fb5ccc98782f654778cb8d96ba8a998304f9a51f
>
> This needed some massaging to work around not having 4fe2c963154c3
> ("io_uring: add support for link with drain"). I've fixed it up and
> queued it.
>
>> 935d1e45908afb8853c497f2c2bbbb685dec51dc
>
> I think that Greg's scripts didn't like how much this code moved around
> and refused to deal with it. I've verified patching did the right thing
> and queued it up.
>
>> 498ccd9eda49117c34e0041563d0da6ac40e52b8
>
> This one needed massaging to work around missing 75b28affdd6ae
> ("io_uring: allocate the two rings together") in the stable tree. I've
> fixed it up and queued it up.
>
>
> Jens, could you please take a look at my backport of fb5ccc98782f65:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/tree/queue-5.3/io_uring-fix-broken-links-with-offloading.patch
>
> And 498ccd9eda491:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/tree/queue-5.3/io_uring-used-cached-copies-of-sq-dropped-and-cq-ove.patch
>
> And confirm I did the right thing?
Of course, I'll take a look right now. Thanks for taking care of these!
--
Jens Axboe
next prev parent reply other threads:[~2019-10-27 12:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-26 23:33 io_uring stable 5.3 backports Jens Axboe
2019-10-27 7:22 ` Greg KH
2019-10-27 8:52 ` Sasha Levin
2019-10-27 12:01 ` Jens Axboe [this message]
2019-10-27 12:06 ` Jens Axboe
2019-10-27 13:48 ` Sasha Levin
2019-10-27 14:03 ` Jens Axboe
2019-10-27 14:24 ` Sasha Levin
2019-10-27 16:18 ` Jens Axboe
2019-10-27 18:10 ` Sasha Levin
2019-10-27 18:54 ` Jens Axboe
2019-10-27 21:55 ` Sasha Levin
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=f90a0bd3-3074-ee14-dea9-63d520bd72a2@kernel.dk \
--to=axboe@kernel.dk \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).