From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932088Ab2EGRAt (ORCPT ); Mon, 7 May 2012 13:00:49 -0400 Received: from mail-gh0-f174.google.com ([209.85.160.174]:65025 "EHLO mail-gy0-f174.google.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1756791Ab2EGRAq (ORCPT ); Mon, 7 May 2012 13:00:46 -0400 MIME-Version: 1.0 In-Reply-To: <20120507174240.4209c5cb@pyramind.ukuu.org.uk> References: <20120503212151.568.91854.stgit@bob.linux.org.uk> <20120503212219.568.15653.stgit@bob.linux.org.uk> <20120507171126.5beddc27@pyramind.ukuu.org.uk> <1336408208.3638.15.camel@lappy> <20120507174240.4209c5cb@pyramind.ukuu.org.uk> From: Sasha Levin Date: Mon, 7 May 2012 19:00:24 +0200 Message-ID: Subject: Re: [PATCH 3/3] tty_lock: Localise the lock To: Alan Cox Cc: linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > So whatever your trace is showing, that's not the bug. Something more > complicated would appear to be afoot. Oddly enough, tty != tty->link, but the lockdep warning triggers. Any idea why it might happen?