From: "'gregkh@linuxfoundation.org'" <gregkh@linuxfoundation.org>
To: Dexuan Cui <decui@microsoft.com>
Cc: "'stable@vger.kernel.org'" <stable@vger.kernel.org>,
'Wang Jian' <jianjian.wang1@gmail.com>,
Long Li <longli@microsoft.com>, KY Srinivasan <kys@microsoft.com>,
Stephen Hemminger <sthemmin@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
Josh Poulson <jopoulso@microsoft.com>,
"Michael Kelley (EOSG)" <Michael.H.Kelley@microsoft.com>
Subject: Re: [PATCH 0/4] [for linux-4.4.y only] Hyper-V: backport 4 KVP fixes
Date: Thu, 18 Oct 2018 19:10:38 +0200 [thread overview]
Message-ID: <20181018171038.GJ11159@kroah.com> (raw)
In-Reply-To: <PU1P153MB0169B5A0C7CE1DFA44E15E55BFFF0@PU1P153MB0169.APCP153.PROD.OUTLOOK.COM>
On Wed, Oct 17, 2018 at 01:22:47AM +0000, Dexuan Cui wrote:
>
> Recently Wang Jian reported some KVP issues on the v4.4 kernel:
> https://github.com/LIS/lis-next/issues/593:
> e.g. the /var/lib/hyperv/.kvp_pool_* files can not be updated, and
> sometimes if the hv_kvp_daemon doesn't timely start, the host may not
> be able to query the VM's IP address via KVP.
>
> I identified these 4 mainline patches to fix the issues. The patches
> can be applied cleanly to the latest 4.4.y branch (currently it's
> v4.4.161).
>
> The first 3 are simply cherry-picked from the mainline, and the 4th
> has to be reworked for the v4.4 kernel.
>
> Wang Jian tested the 4 patches, and the issues can be fixed.
> I also did some tests and found no regression.
>
All now queued up, and I added the last one to 4.9.y as well. If it
shouldn't be there, please let me know.
thanks,
greg k-h
next prev parent reply other threads:[~2018-10-19 1:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-17 1:22 [PATCH 0/4] [for linux-4.4.y only] Hyper-V: backport 4 KVP fixes Dexuan Cui
2018-10-18 17:10 ` 'gregkh@linuxfoundation.org' [this message]
2018-10-18 18:54 ` 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=20181018171038.GJ11159@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Michael.H.Kelley@microsoft.com \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=jianjian.wang1@gmail.com \
--cc=jopoulso@microsoft.com \
--cc=kys@microsoft.com \
--cc=longli@microsoft.com \
--cc=stable@vger.kernel.org \
--cc=sthemmin@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