From: Greg KH <gregkh@linuxfoundation.org>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: tglx@linutronix.de, dvhart@infradead.org,
heiko.carstens@de.ibm.com, mingo@kernel.org,
peterz@infradead.org, sashal@kernel.org, stli@linux.ibm.com,
stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] futex: Cure exit race" failed to apply to 4.14-stable tree
Date: Mon, 18 Feb 2019 13:20:20 +0100 [thread overview]
Message-ID: <20190218122020.GB30260@kroah.com> (raw)
In-Reply-To: <20190217113430.6noyzzaq7r4evpxv@debian>
On Sun, Feb 17, 2019 at 11:34:30AM +0000, Sudip Mukherjee wrote:
> Hi Greg,
>
> On Mon, Dec 24, 2018 at 12:52:22PM +0100, gregkh@linuxfoundation.org wrote:
> >
> > The patch below does not apply to the 4.14-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>.
>
> The attached backported patch should apply to 4.14-stable tree.
>
> I think we have a real usecase which is triggering this error and I was
> still in the middle of debugging that. But my initial analysis was
> showing that the userspace thread was stuck in the indefinite loop.
> I have a reliable reproducer of the problem and will setup a test
> tomorrow and confirm.
Now applied, thanks.
greg k-h
prev parent reply other threads:[~2019-02-18 12:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-24 11:52 FAILED: patch "[PATCH] futex: Cure exit race" failed to apply to 4.14-stable tree gregkh
2019-02-17 11:34 ` Sudip Mukherjee
2019-02-17 11:53 ` Thomas Gleixner
2019-02-17 12:27 ` Sudip Mukherjee
2019-02-17 17:59 ` Thomas Gleixner
2019-02-18 8:26 ` Stefan Liebler
2019-02-19 10:34 ` Sudip Mukherjee
2019-02-18 12:20 ` 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=20190218122020.GB30260@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dvhart@infradead.org \
--cc=heiko.carstens@de.ibm.com \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=stli@linux.ibm.com \
--cc=sudipm.mukherjee@gmail.com \
--cc=tglx@linutronix.de \
/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).