From: Greg KH <gregkh@linuxfoundation.org>
To: "K. Y. Srinivasan" <kys@microsoft.com>
Cc: linux-kernel@vger.kernel.org, devel@linuxdriverproject.org,
olaf@aepfle.de, apw@canonical.com, vkuznets@redhat.com,
jasowang@redhat.com
Subject: Re: [PATCH 1/3] Drivers: hv: balloon: don't crash when memory is added in non-sorted order
Date: Sat, 30 Apr 2016 14:02:42 -0700 [thread overview]
Message-ID: <20160430210242.GA30882@kroah.com> (raw)
In-Reply-To: <1461955519-32276-1-git-send-email-kys@microsoft.com>
On Fri, Apr 29, 2016 at 11:45:17AM -0700, K. Y. Srinivasan wrote:
> From: Vitaly Kuznetsov <vkuznets@redhat.com>
>
> When we iterate through all HA regions in handle_pg_range() we have an
> assumption that all these regions are sorted in the list and the
> 'start_pfn >= has->end_pfn' check is enough to find the proper region.
> Unfortunately it's not the case with WS2016 where host can hot-add regions
> in a different order. We end up modifying the wrong HA region and crashing
> later on pages online. Modify the check to make sure we found the region
> we were searching for while iterating. Fix the same check in pfn_covered()
> as well.
>
> Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
> Signed-off-by: K. Y. Srinivasan <kys@microsoft.com>
> ---
> drivers/hv/hv_balloon.c | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
I only received patch 1/3 here, what happened to the other 2?
Can you resend the whole series?
thanks,
greg k-h
next parent reply other threads:[~2016-04-30 21:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1461955494-32235-1-git-send-email-kys@microsoft.com>
[not found] ` <1461955519-32276-1-git-send-email-kys@microsoft.com>
2016-04-30 21:02 ` Greg KH [this message]
2016-04-30 21:38 ` [PATCH 1/3] Drivers: hv: balloon: don't crash when memory is added in non-sorted order KY Srinivasan
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=20160430210242.GA30882@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=apw@canonical.com \
--cc=devel@linuxdriverproject.org \
--cc=jasowang@redhat.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=olaf@aepfle.de \
--cc=vkuznets@redhat.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.