stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Daniel Jordan <daniel.m.jordan@oracle.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Sasha Levin <sashal@kernel.org>
Cc: Steffen Klassert <steffen.klassert@secunet.com>
Cc: linux-kernel@vger.kernel.org
Cc: stable@vger.kernel.org
Cc: stable@vger.kernel.org
Subject: Re: [PATCH for 4.19-stable] padata: fix null pointer deref of pd->pinst
Date: Sat, 15 Feb 2020 15:01:18 +0000	[thread overview]
Message-ID: <20200215150118.B22262084E@mail.kernel.org> (raw)
In-Reply-To: <20200214182821.337706-1-daniel.m.jordan@oracle.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 645 bytes --]

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?

-- 
Thanks,
Sasha

  parent reply	other threads:[~2020-02-15 15:04 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 [this message]
2020-02-17  2:11   ` Yang Yingliang

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=20200215150118.B22262084E@mail.kernel.org \
    --to=sashal@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).