[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <5E49F64A.2070904@huawei.com>
Date: Mon, 17 Feb 2020 10:11:22 +0800
From: Yang Yingliang <yangyingliang@...wei.com>
To: Sasha Levin <sashal@...nel.org>,
Daniel Jordan <daniel.m.jordan@...cle.com>
CC: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Herbert Xu <herbert@...dor.apana.org.au>,
Steffen Klassert <steffen.klassert@...unet.com>,
<linux-kernel@...r.kernel.org>, <stable@...r.kernel.org>
Subject: Re: [PATCH for 4.19-stable] padata: fix null pointer deref of
pd->pinst
Hi,
On 2020/2/15 23:01, Sasha Levin wrote:
> Hi,
>
> [This is an automated email]
>
> This commit has been processed because it contains a "Fixes:" tag,
> fixing commit: dc34710a7aba ("padata: Remove broken queue flushing").
>
> The bot has tested the following trees: v5.5.3, v5.4.19, v4.19.103.
>
> v5.5.3: Build failed! Errors:
> kernel/padata.c:460:4: error: ‘struct parallel_data’ has no member named ‘pinst’
>
> v5.4.19: Build failed! Errors:
> kernel/padata.c:460:4: error: ‘struct parallel_data’ has no member named ‘pinst’
>
> v4.19.103: Build OK!
>
> NOTE: The patch will not be queued to stable trees until it is upstream.
>
> How should we proceed with this patch?
The commit bbefa1dd6a6d ("crypto: pcrypt - Avoid deadlock by using
per-instance padata queues") that merged
on linux-5.4.y and linux-5.5.y changes struct parallel_data, so this
patch it's only needed on linux-4.19.y.
>
Powered by blists - more mailing lists