[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <8b98b1e0-2161-6c58-573c-613940e0f31e@huawei.com>
Date: Sat, 4 Feb 2017 18:32:46 +0800
From: Yisheng Xie <xieyisheng1@...wei.com>
To: Andy Lutomirski <luto@...nel.org>, <linux-crypto@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, Matt Mackall <mpm@...enic.com>,
Herbert Xu <herbert@...dor.apana.org.au>,
Rusty Russell <rusty@...tcorp.com.au>,
"Jens Axboe" <axboe@...com>, Matt Mullins <mmullins@...x.us>,
Xishi Qiu <qiuxishi@...wei.com>,
Hanjun Guo <guohanjun@...wei.com>
Subject: Re: [PATCH resend 4.9] hw_random: Don't use a stack buffer in
add_early_randomness()
hi, Matt,
Thanks for your reply.
On 2017/2/4 12:34, Matt Mullins wrote:
> On Sat, Feb 04, 2017 at 11:47:38AM +0800, Yisheng Xie wrote:
>> On 2016/10/18 1:06, Andy Lutomirski wrote:
>>> hw_random carefully avoids using a stack buffer except in
>>> add_early_randomness(). This causes a crash in virtio_rng if
>>> CONFIG_VMAP_STACK=y.
>> I try to understand this patch, but I do not know why it will cause
>> a crash in virtio_rng with CONFIG_VMAP_STACK=y?
>> Could you please give me more info. about it.
>
> My original report was
> https://lkml.kernel.org/r/20161016002151.GA18235@hydra.tuxags.com.
>
> The virtio ring APIs use scatterlists to keep track of the buffers, and
> scatterlist requires addresses to be in the kernel direct-mapped address range.
> This is not the case for vmalloc()ed addresses, such as the original on-stack
> "bytes" array when VMAP_STACK=y.
>
I see, and will check the logic to get more detail about it.
Thanks.
Yisheng Xie
Powered by blists - more mailing lists