Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Mon, 21 Jan 2019 16:36:28 +0300
From:   Dan Carpenter <dan.carpenter@oracle.com>
To:     Ajay Kaher <akaher@vmware.com>
Cc:     linux-pci@vger.kernel.org, haiyangz@microsoft.com,
        linux-kernel@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>,
        devel@linuxdriverproject.org
Subject: Re: [PATCH 1/3] PCI: hv: Allocate physically contiguous hypercall
 params buffer
Message-ID: <20190121133628.GI4482@kadam>
References: <1547758038-5255-1-git-send-email-akaher@vmware.com>
 <1547758038-5255-2-git-send-email-akaher@vmware.com>
 <20190121131942.GH4482@kadam>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20190121131942.GH4482@kadam>
User-Agent: Mutt/1.9.4 (2018-02-28)
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Mon, Jan 21, 2019 at 04:19:42PM +0300, Dan Carpenter wrote:
> On Fri, Jan 18, 2019 at 02:17:16AM +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.
> > 
> 
> Since you're going to need to resend this anyway, can you add in the
> commit message what this looks like from a user perspective?  Presumably
> it's an occasional crash?
> 

Never mind.  I didn't realize this was a two year old patch.

regards,
dan carpenter