On Sun, 17 Feb 2019, Sudip Mukherjee wrote:
Hi Thomas,
On Sun, Feb 17, 2019 at 11:53 AM Thomas Gleixner tglx@linutronix.de wrote:
On Sun, 17 Feb 2019, Sudip Mukherjee wrote:
Hi Greg,
On Mon, Dec 24, 2018 at 12:52:22PM +0100, gregkh@linuxfoundation.org wrote:
<snip> > > 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. > > There are more patches in that area and you also need a fixed glibc.
I can see 1a1fb985f2e2 ("futex: Handle early deadlock return correctly") is already there in 4.14-stable. Is anything else missing, other than this one?
glibc might be a problem, but lets see what can be done.
Those two are the kernel side of affairs I think.
The relevant glibc commits are:
8f9450a0b7a9e78267e8ae1ab1000ebca08e473e 823624bdc47f1f80109c9c52dee7939b9386d708
Thanks,
tglx