From: Sasha Levin <sashal@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-kernel@microsoft.com
Cc: kys@microsoft.com
Cc: haiyangz@microsoft.com
Cc: sthemmin@microsoft.com
Cc: linux-kernel@vger.kernel.org
Subject: [GIT PULL v3] Hyper-V commits for 5.0
Date: Thu, 10 Jan 2019 10:24:31 -0500 [thread overview]
Message-ID: <20190110152432.75529214C6@mail.kernel.org> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
The following changes since commit bfeffd155283772bbe78c6a05dec7c0128ee500c:
Linux 5.0-rc1 (2019-01-06 17:08:20 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git tags/hyperv-fixes-signed
for you to fetch changes up to b5679cebf780c6f1c2451a73bf1842a4409840e7:
vmbus: fix subchannel removal (2019-01-09 19:20:31 -0500)
- ----------------------------------------------------------------
Three bug fixes for different parts of the hyper-v code:
- Fix for a lockup when changing NIC's MTU from Dexuan.
- Fix of use of uninitialized memory from Dexuan.
- Fix for memory corruption caused by ballooning from Vitaly.
All 3 were tested internally.
- ----------------------------------------------------------------
Dexuan Cui (2):
Drivers: hv: vmbus: Check for ring when getting debug info
vmbus: fix subchannel removal
Vitaly Kuznetsov (1):
hv_balloon: avoid touching uninitialized struct page during tail onlining
drivers/hv/channel.c | 9 +----
drivers/hv/hv_balloon.c | 10 +++---
drivers/hv/ring_buffer.c | 31 ++++++++---------
drivers/hv/vmbus_drv.c | 91 ++++++++++++++++++++++++++++++++----------------
include/linux/hyperv.h | 5 +--
5 files changed, 86 insertions(+), 60 deletions(-)
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEE4n5dijQDou9mhzu83qZv95d3LNwFAlw3YyQACgkQ3qZv95d3
LNyE8w/+Of8iNo0BtW4BQNIX+vF2jtP2fzvqyZ01wGC2FHR0MRiwLwG24yvZ3z/k
xqihTkbK2aiZ2r1LT9Z3nkd0xxpkj5GBN/9voW3xJDukimUlor+wEBl/TID1WdgT
sl4u+pI/2kfLeWYf9sCkoO0oZ/AiRmuC0PG4tLB8o21y13Ngd1lW1cIpCFciX2OJ
LnNgEHi5wfLipEj7wJEKJPh095CaDtBpsnw++5Ef5pYbJBVqH9QPtqWSfCWY0+vA
PEQmpij4VAtjXhyPixoc8bi9AxiHw6bqRk94jowyeH8M5Cn1gX3uY0hJmhjVPYSY
6/odsGf5ZUrnGYBd0DuJsdQwKKzaZGbL4M6dnJML1yKsBnU7lzfHTW8OaE8ob9oX
13lBF9ii2YOiPdzB1SeQ3unnHYyyVlfuYGJwKM+51KU2BWnSWsq7Jaw6MeNEXwqK
T1Deiiqmg5hdRTlsmS77uywkkrcS+Y+Fu9R9RFeddYj/gTekyWCDhZJ7Sf2AtkXP
bxjlPwFuTmOdpz6VaM6kvgJLA1VkalSHmf0dXKlYibLiS5uonVVydYUOv6wMiuJc
mh6XeVv28aPyYAeEC3dkITqAAPx1Grijp6k066cvcIYz2qD31dlKi6OXjeuIlHLN
O3ddwIzGTPrTTxtvj9L1aIaeRxVwNdFFi1XZjzvk2vGsoOj/gGk=
=SmAD
-----END PGP SIGNATURE-----
next reply other threads:[~2019-01-10 15:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-10 15:24 Sasha Levin [this message]
2019-01-11 9:15 ` [GIT PULL v3] Hyper-V commits for 5.0 Greg KH
2019-01-11 14:10 ` Sasha Levin
2019-01-11 14:30 ` Greg KH
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=20190110152432.75529214C6@mail.kernel.org \
--to=sashal@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.