From: Jens Axboe <axboe@kernel.dk>
To: Sasha Levin <sashal@kernel.org>
Cc: stable@vger.kernel.org, "Agarwal, Anchal" <anchalag@amazon.com>
Subject: Re: Request for patch inclusion for 5.4-stable
Date: Wed, 1 Jul 2020 22:07:55 -0600 [thread overview]
Message-ID: <a35028c3-6cb7-99dc-83f0-5b96f015d2c4@kernel.dk> (raw)
In-Reply-To: <20200702013140.GG2687961@sasha-vm>
On 7/1/20 7:31 PM, Sasha Levin wrote:
> On Wed, Jul 01, 2020 at 12:24:17PM -0600, Jens Axboe wrote:
>> Hi,
>>
>> There's no upstream variant of this, as that would require backporting
>> all the io-wq changes from 5.5 and on. Hence I made a one-off that
>> ensures that we don't leak memory if we have async work items that
>> need active cancelation (like socket IO).
>>
>> Can we get this queued up for 5.4? I've tested it and the original
>> reporter has as well.
>
> I've added the previous paragraph which explains why there is no
> upstream version of this into the commit message and queued it for 5.4,
> thank you!
Perfect, thanks Sasha!
--
Jens Axboe
prev parent reply other threads:[~2020-07-02 4:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-01 18:24 Request for patch inclusion for 5.4-stable Jens Axboe
2020-07-02 1:31 ` Sasha Levin
2020-07-02 4:07 ` 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 \
--in-reply-to=a35028c3-6cb7-99dc-83f0-5b96f015d2c4@kernel.dk \
--to=axboe@kernel.dk \
--cc=anchalag@amazon.com \
--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