> Cc: KY Srinivasan <k...@microsoft.com>; Haiyang Zhang
> > <haiya...@microsoft.com>; Bjorn Helgaas <bhelg...@google.com>;
> > de...@linuxdriverproject.org; linux-ker...@vger.kernel.org; linux-
> > p...@vger.kernel.org
> > Subject: Re: [PATCH] pci-hyperv: use k
Helgaas <bhelg...@google.com>;
> de...@linuxdriverproject.org; linux-ker...@vger.kernel.org; linux-
> p...@vger.kernel.org
> Subject: Re: [PATCH] pci-hyperv: use kmalloc to allocate hypercall params
> buffer
>
> On Tue, 8 Nov 2016 14:04:38 -0800
> Long Li <
To: Bjorn Helgaas <helg...@kernel.org>; Long Li <lon...@microsoft.com>
> > Cc: de...@linuxdriverproject.org
> > Subject: Re: [PATCH] pci-hyperv: use kmalloc to allocate hypercall
> > params buffer
> >
> > Hi,
> >
> > Is the double semicolon a typo?
&g
ject.org
> Subject: Re: [PATCH] pci-hyperv: use kmalloc to allocate hypercall params
> buffer
>
> Hi,
>
> Is the double semicolon a typo?
Yes; it is a typo.
K. Y
>
> Thanks,
>
> Cathy
>
> diff --git a/drivers/pci/host/pci-hyperv.c b/drivers/pci/host/pci-hyp
On Tue, 8 Nov 2016 14:04:38 -0800
Long Li wrote:
> + spin_lock_irqsave(>retarget_msi_interrupt_lock, flags);
> +
> + params = >retarget_msi_interrupt_params;
> + memset(params, 0, sizeof(*params));
> + params->partition_id = HV_PARTITION_ID_SELF;
>
Hi,
Is the double semicolon a typo?
Thanks,
Cathy
diff --git a/drivers/pci/host/pci-hyperv.c b/drivers/pci/host/pci-hyperv.c
index 763ff87..ca553df 100644
--- a/drivers/pci/host/pci-hyperv.c
+++ b/drivers/pci/host/pci-hyperv.c
@@ -378,6 +378,8 @@ struct hv_pcibus_device {
struct
On Tue, Nov 08, 2016 at 02:04:38PM -0800, Long Li wrote:
> From: Long Li
>
> hv_do_hypercall assumes that we pass a segment from a physically
> continuous buffer. Buffer allocated on the stack may not work if
> CONFIG_VMAP_STACK=y is set.
>
> Change to use kmalloc to
Helgaas <bhelg...@google.com>;
> de...@linuxdriverproject.org; linux-...@vger.kernel.org; linux-
> ker...@vger.kernel.org; Long Li <lon...@microsoft.com>
> Subject: Re: [PATCH] pci-hyperv: use kmalloc to allocate hypercall params
> buffer
>
> On Tue, Nov 08, 2016 at 02:04:
On Tue, Nov 08, 2016 at 02:04:38PM -0800, Long Li wrote:
> From: Long Li
>
> hv_do_hypercall assumes that we pass a segment from a physically
> continuous buffer. Buffer allocated on the stack may not work if
> CONFIG_VMAP_STACK=y is set.
>
> Change to use kmalloc to
microsoft.com>;
> linux-ker...@vger.kernel.org; Bjorn Helgaas <bhelg...@google.com>;
> de...@linuxdriverproject.org
> Subject: RE: [Resend] [PATCH] pci-hyperv: use kmalloc to allocate hypercall
> params buffer
>
> This sender failed our fraud detection checks and may not be
From: Long Li
hv_do_hypercall assumes that we pass a segment from a physically
continuous buffer. Buffer allocated on the stack may not work if
CONFIG_VMAP_STACK=y is set.
Change to use kmalloc to allocate this buffer.
The v2 patch adds locking to access the pre-allocated
> de...@linuxdriverproject.org; linux-ker...@vger.kernel.org; linux-
> p...@vger.kernel.org
> Subject: RE: [Resend] [PATCH] pci-hyperv: use kmalloc to allocate hypercall
> params buffer
>
>
>
> > -Original Message-
> > From: Greg KH [mailto:gre...@linuxfound
Helgaas <bhelg...@google.com>;
> de...@linuxdriverproject.org; linux-ker...@vger.kernel.org; linux-
> p...@vger.kernel.org
> Subject: Re: [Resend] [PATCH] pci-hyperv: use kmalloc to allocate hypercall
> params buffer
>
> On Tue, Nov 08, 2016 at 12:14:14AM -0800, Long Li wrote:
>
On Tue, Nov 08, 2016 at 12:14:14AM -0800, Long Li wrote:
> From: Long Li
>
> hv_do_hypercall assumes that we pass a segment from a physically continuous
> buffer. Buffer allocated on the stack may not work if CONFIG_VMAP_STACK=y is
> set. Use kmalloc to allocate this
From: Long Li
hv_do_hypercall assumes that we pass a segment from a physically continuous
buffer. Buffer allocated on the stack may not work if CONFIG_VMAP_STACK=y is
set. Use kmalloc to allocate this buffer.
Signed-off-by: Long Li
Reported-by:
15 matches
Mail list logo