From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jarek Poplawski <jarkao2@gmail.com>
Subject: Re: Deadlock in IPv6 code while garbage collection on the rwlock
	protecting the routing tree.
Date: Tue, 26 Jan 2010 09:48:17 +0000
Message-ID: <20100126094817.GA7780@ff.dom.local>
References: <20100123.022210.56302976.davem@davemloft.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: shemminger@vyatta.com, djohnson@starentnetworks.com,
	sakkiped@starentnetworks.com, netdev@vger.kernel.org
To: David Miller <davem@davemloft.net>
Return-path: <netdev-owner@vger.kernel.org>
Received: from mail-fx0-f220.google.com ([209.85.220.220]:44504 "EHLO
	mail-fx0-f220.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1751323Ab0AZJsW (ORCPT
	<rfc822;netdev@vger.kernel.org>); Tue, 26 Jan 2010 04:48:22 -0500
Received: by fxm20 with SMTP id 20so134914fxm.21
        for <netdev@vger.kernel.org>; Tue, 26 Jan 2010 01:48:21 -0800 (PST)
Content-Disposition: inline
In-Reply-To: <20100123.022210.56302976.davem@davemloft.net>
Sender: netdev-owner@vger.kernel.org
List-ID: <netdev.vger.kernel.org>

On 23-01-2010 11:22, David Miller wrote:
> This is all well and good, but meanwhile someone does need to
> fix the deadlock originally reported here :-)

I hope I miss something ;-) but I can't see this deadlock; the
write_lock_bh(&table->tb6_lock) is taken from a timer in this case,
not from the thread holding read_lock_bh(&table->tb6_lock).

Jarek P.