From: Greg KH <greg@kroah.com>
To: Ajay Kaher <akaher@vmware.com>
Cc: kys@microsoft.com, haiyangz@microsoft.com, jloeser@microsoft.com,
sthemmin@microsoft.com, sashal@kernel.org,
mikelley@microsoft.com, decui@microsoft.com,
stable@vger.kernel.org, srivatsab@vmware.com,
amakhalov@vmware.com
Subject: Re: [PATCH 1/3] PCI: hv: Allocate physically contiguous hypercall params buffer
Date: Wed, 23 Jan 2019 09:01:19 +0100 [thread overview]
Message-ID: <20190123080119.GC7597@kroah.com> (raw)
In-Reply-To: <1548257912-18273-2-git-send-email-akaher@vmware.com>
On Wed, Jan 23, 2019 at 09:08:30PM +0530, Ajay Kaher wrote:
> hv_do_hypercall() assumes that we pass a segment from a physically
> contiguous buffer. A buffer allocated on the stack may not work if
> CONFIG_VMAP_STACK=y is set.
>
> Use kmalloc() to allocate this buffer.
>
> Signed-off-by: Ajay Kaher <akaher@vmware.com>
> ---
> drivers/pci/host/pci-hyperv.c | 29 +++++++++++++++++++----------
> 1 file changed, 19 insertions(+), 10 deletions(-)
No hint as to what the upstream git commit id is here?
Same for all of these patches, I'm not reviewing beyond this one...
next prev parent reply other threads:[~2019-01-23 8:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-23 15:38 [PATCH 0/3] PCI: hv: Use vPCI protocol version 1.2 for v4.9 Ajay Kaher
2019-01-23 8:00 ` Greg KH
2019-01-23 8:02 ` Greg KH
2019-01-23 12:02 ` Ajay Kaher
2019-01-23 12:08 ` Greg KH
2019-01-23 15:38 ` [PATCH 1/3] PCI: hv: Allocate physically contiguous hypercall params buffer Ajay Kaher
2019-01-23 8:01 ` Greg KH [this message]
2019-01-23 15:38 ` [PATCH 2/3] PCI: hv: Add vPCI version protocol negotiation Ajay Kaher
2019-01-23 15:38 ` [PATCH 3/3] PCI: hv: Use vPCI protocol version 1.2 for v4.9 Ajay Kaher
-- strict thread matches above, loose matches on Subject: below --
2019-01-17 20:47 [PATCH 0/3] " Ajay Kaher
2019-01-17 20:47 ` [PATCH 1/3] PCI: hv: Allocate physically contiguous hypercall params buffer Ajay Kaher
2019-01-17 14:57 ` Bjorn Helgaas
2019-01-21 13:19 ` Dan Carpenter
2019-01-21 13:36 ` Dan Carpenter
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=20190123080119.GC7597@kroah.com \
--to=greg@kroah.com \
--cc=akaher@vmware.com \
--cc=amakhalov@vmware.com \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=jloeser@microsoft.com \
--cc=kys@microsoft.com \
--cc=mikelley@microsoft.com \
--cc=sashal@kernel.org \
--cc=srivatsab@vmware.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 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.