From: Sasha Levin <sashal@kernel.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: stable@vger.kernel.org
Subject: Re: io_uring stable 5.3 backports
Date: Sun, 27 Oct 2019 09:48:32 -0400 [thread overview]
Message-ID: <20191027134832.GD1560@sasha-vm> (raw)
In-Reply-To: <f90a0bd3-3074-ee14-dea9-63d520bd72a2@kernel.dk>
On Sun, Oct 27, 2019 at 06:01:03AM -0600, Jens Axboe wrote:
>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.
How much "secret sauce" does your internal tree have? Is it something we
can peek into to make sure we don't miss fixes?
--
Thanks,
Sasha
next prev parent reply other threads:[~2019-10-27 13:48 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
2019-10-27 12:06 ` Jens Axboe
2019-10-27 13:48 ` Sasha Levin [this message]
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=20191027134832.GD1560@sasha-vm \
--to=sashal@kernel.org \
--cc=axboe@kernel.dk \
--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).