From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Dexuan Cui <decui@microsoft.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
Sunil Muthuswamy <sunilmut@microsoft.com>,
"David S. Miller" <davem@davemloft.net>,
Sasha Levin <sashal@kernel.org>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: Request vsock and hv_sock patches to be backported for linux-5.2.y, linux-4.19.y and linux-4.14.y
Date: Wed, 31 Jul 2019 11:30:49 +0200 [thread overview]
Message-ID: <20190731093049.GC18269@kroah.com> (raw)
In-Reply-To: <PU1P153MB0169AD4EB10548EACCED82C2BFDF0@PU1P153MB0169.APCP153.PROD.OUTLOOK.COM>
On Wed, Jul 31, 2019 at 06:41:10AM +0000, Dexuan Cui wrote:
> Hi,
> Sunil Muthuswamy <sunilmut@microsoft.com> made some important fixes for
> hv_sock recently. I and Sunil think it would be great to backport the
> fixes to the longterm stable kernels.
>
> Since hv_sock was firstly introduced in v4.14, we only care about
> v4.14, v4.19 and v5.2.
>
> For linux-5.2.y (currently it's v5.2.4), only one patch is missing.
> The mainline commit ID is:
> d5afa82c977e ("vsock: correct removal of socket from the list")
> It can be cleanly cherry-picked from the mainline.
>
>
> For linux-4.19.y (currently it's v4.19.62), 3 patches are missing.
> The mainline commit IDs are:
> cb359b604167 ("hvsock: fix epollout hang from race condition")
> a9eeb998c28d ("hv_sock: Add support for delayed close")
> d5afa82c977e ("vsock: correct removal of socket from the list")
> They can be cleanly cherry-picked from the mainline, in the listed order here.
> Note: it looks the first commit (cb359b604167) has been queued.
>
>
> For linux-4.14.y (currently it's v4.14.134), 4 patches are missing.
> The mainline commit IDs are:
> cb359b604167 ("hvsock: fix epollout hang from race condition")
> 3b4477d2dcf2 ("VSOCK: use TCP state constants for sk_state")
> a9eeb998c28d ("hv_sock: Add support for delayed close")
> d5afa82c977e ("vsock: correct removal of socket from the list")
> The third patch (a9eeb998c28d) needs small manual adjustments, and please
> use the attached backported patch for it; the other 3 patches can be cleanly
> cherry-picked from the mainline, in the listed order here.
> Note: it looks the first commit (cb359b604167) has been queued.
I have not taken 3b4477d2dcf2 ("VSOCK: use TCP state constants for
sk_state") for 4.14.y as it doesn't look like you really needed it. Are
you sure you did?
The other ones are now queued up, please let me know if I have messed
anythign up.
thanks,
greg k-h
next prev parent reply other threads:[~2019-07-31 9:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-31 6:41 Request vsock and hv_sock patches to be backported for linux-5.2.y, linux-4.19.y and linux-4.14.y Dexuan Cui
2019-07-31 9:24 ` Greg Kroah-Hartman
2019-07-31 9:26 ` Greg Kroah-Hartman
2019-07-31 9:30 ` Greg Kroah-Hartman [this message]
2019-07-31 20:13 ` Dexuan Cui
2019-08-01 6:21 ` Greg Kroah-Hartman
2019-08-01 16:24 ` Dexuan Cui
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=20190731093049.GC18269@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=davem@davemloft.net \
--cc=decui@microsoft.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=stefanha@redhat.com \
--cc=sunilmut@microsoft.com \
/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).