stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: David Hildenbrand <david@redhat.com>
Cc: akpm@linux-foundation.org, bhe@redhat.com, boqun.feng@gmail.com,
	dyoung@redhat.com, josh@joshtriplett.org, paulmck@kernel.org,
	peterz@infradead.org, stable@vger.kernel.org,
	torvalds@linux-foundation.org, vgoyal@redhat.com
Subject: Re: FAILED: patch "[PATCH] proc/vmcore: fix possible deadlock on concurrent mmap and" failed to apply to 5.16-stable tree
Date: Mon, 4 Apr 2022 12:40:52 +0200	[thread overview]
Message-ID: <YkrLNL47V+dhPFF+@kroah.com> (raw)
In-Reply-To: <5a220426-6b83-6a0e-5af0-ee4c76e72c79@redhat.com>

On Mon, Apr 04, 2022 at 12:17:47PM +0200, David Hildenbrand wrote:
> On 02.04.22 13:36, gregkh@linuxfoundation.org wrote:
> > 
> > The patch below does not apply to the 5.16-stable tree.
> > If someone wants it applied there, or to any other stable or longterm
> > tree, then please email the backport, including the original git commit
> > id to <stable@vger.kernel.org>.
> > 
> 
> I don't think we need that particular patch in -stable. The deadlock
> shouldn't really happen in practice (concurrent addition/removal of a
> callback doesn't really happen in a kdump anvironment). Thanks.

Ok, I'll go drop it from 5.17-stable, thanks.

greg k-h

      reply	other threads:[~2022-04-04 10:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-02 11:36 FAILED: patch "[PATCH] proc/vmcore: fix possible deadlock on concurrent mmap and" failed to apply to 5.16-stable tree gregkh
2022-04-04 10:17 ` David Hildenbrand
2022-04-04 10:40   ` Greg KH [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=YkrLNL47V+dhPFF+@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=bhe@redhat.com \
    --cc=boqun.feng@gmail.com \
    --cc=david@redhat.com \
    --cc=dyoung@redhat.com \
    --cc=josh@joshtriplett.org \
    --cc=paulmck@kernel.org \
    --cc=peterz@infradead.org \
    --cc=stable@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=vgoyal@redhat.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 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).