From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756069AbcBEVWd (ORCPT ); Fri, 5 Feb 2016 16:22:33 -0500 Received: from mail-wm0-f51.google.com ([74.125.82.51]:34979 "EHLO mail-wm0-f51.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750721AbcBEVWb (ORCPT ); Fri, 5 Feb 2016 16:22:31 -0500 MIME-Version: 1.0 In-Reply-To: References: <20160120130201.GA1027@worktop> <569FB10F.4080205@hurleysoftware.com> <56A118C4.9050402@hurleysoftware.com> <56B180F8.8030901@hurleysoftware.com> <56B25050.9070003@hurleysoftware.com> <56B39C7A.2080606@hurleysoftware.com> From: Dmitry Vyukov Date: Fri, 5 Feb 2016 22:22:10 +0100 Message-ID: Subject: Re: tty: deadlock between n_tracerouter_receivebuf and flush_to_ldisc To: Peter Hurley Cc: Peter Zijlstra , Jiri Slaby , One Thousand Gnomes , Greg Kroah-Hartman , LKML , J Freyensee , syzkaller , Kostya Serebryany , Alexander Potapenko , Sasha Levin , Eric Dumazet Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Feb 4, 2016 at 7:48 PM, Dmitry Vyukov wrote: >>>>> Hopefully, once the problem with the bad stacktraces are fixed, the >>>>> actual circular lock dependencies will be clear. >> >>> Found a bug in lockdep. Yes, the first stack is correct, and the saved >>> stack is just a random, unrelated stack. Will mail a fix. >> >> Ok, so with the lockdep bug fixed, those reports should now have the >> correct stack traces. >> >> I'd appreciate if you could re-generate the original report, so I can examine >> if my speculative fix was appropriate. >> >> And then if you would re-generate the more recent report, I'll relook at >> that. > > Working hard on it now. No luck so far. I will leave it running, but I will be OOO whole next week.