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 04:52:04 -0400 [thread overview]
Message-ID: <20191027085204.GA1560@sasha-vm> (raw)
In-Reply-To: <efc9278b-de72-40b2-9a0a-48df0c64edc1@kernel.dk>
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.
>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?
--
Thanks,
Sasha
next prev parent reply other threads:[~2019-10-27 8:52 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 [this message]
2019-10-27 12:01 ` Jens Axboe
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=20191027085204.GA1560@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