All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yang Yingliang <yangyingliang@huawei.com>
To: Sasha Levin <sashal@kernel.org>,
	Daniel Jordan <daniel.m.jordan@oracle.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	Steffen Klassert <steffen.klassert@secunet.com>,
	<linux-kernel@vger.kernel.org>, <stable@vger.kernel.org>
Subject: Re: [PATCH for 4.19-stable] padata: fix null pointer deref of pd->pinst
Date: Mon, 17 Feb 2020 10:11:22 +0800	[thread overview]
Message-ID: <5E49F64A.2070904@huawei.com> (raw)
In-Reply-To: <20200215150118.B22262084E@mail.kernel.org>

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.
>



      reply	other threads:[~2020-02-17  2:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-14 18:28 [PATCH for 4.19-stable] padata: fix null pointer deref of pd->pinst Daniel Jordan
2020-02-14 21:17 ` Greg Kroah-Hartman
2020-02-15 15:01 ` Sasha Levin
2020-02-17  2:11   ` Yang Yingliang [this message]

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=5E49F64A.2070904@huawei.com \
    --to=yangyingliang@huawei.com \
    --cc=daniel.m.jordan@oracle.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=steffen.klassert@secunet.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.