Return-Path: <linux-kernel-owner+w=401wt.eu-S1761444AbYHEM07@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1761444AbYHEM07 (ORCPT <rfc822;w@1wt.eu>);
	Tue, 5 Aug 2008 08:26:59 -0400
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1758781AbYHEMZP
	(ORCPT <rfc822;linux-kernel-outgoing>);
	Tue, 5 Aug 2008 08:25:15 -0400
Received: from mail.deathmatch.net ([70.167.247.36]:45639 "EHLO
	mail.deathmatch.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1759847AbYHEMZO (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Tue, 5 Aug 2008 08:25:14 -0400
Date: Tue, 5 Aug 2008 08:24:08 -0400
From: Bob Copeland <me@bobcopeland.com>
To: Dave Young <hidave.darkstar@gmail.com>
Cc: Jiri Slaby <jirislaby@gmail.com>, Pekka J Enberg <penberg@cs.helsinki.fi>,
       Andrew Morton <akpm@linux-foundation.org>,
       Johannes Berg <johannes@sipsolutions.net>, linux-kernel@vger.kernel.org,
       linux-wireless@vger.kernel.org
Subject: Re: [BUG] wireless : cpu stuck for 61s
Message-ID: <20080805122408.GA5000@hash.localnet>
References: <20080729055731.GA3265@darkstar> <1217334724.10489.47.camel@johannes.berg> <20080730020820.8bcc00e2.akpm@linux-foundation.org> <a8e1da0807300302m35a0a7c0q2ff2e0ab92a69239@mail.gmail.com> <20080730031047.54e13e2d.akpm@linux-foundation.org> <a8e1da0808010032h32c18054g3712466eb40f0acf@mail.gmail.com> <4896D34A.1000005@gmail.com> <a8e1da0808041829sac34939yd9163b02e6b8b515@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <a8e1da0808041829sac34939yd9163b02e6b8b515@mail.gmail.com>
User-Agent: Mutt/1.5.13 (2006-08-11)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 1243
Lines: 28

On Tue, Aug 05, 2008 at 09:29:26AM +0800, Dave Young wrote:
> With the patch I cann't reproduce the bug with 27-rc1 now.
> 
> >  [<c02375a6>] ? debugfs_create_file+0x46/0x210
> >  [<c02375a6>] ? debugfs_create_file+0x46/0x210
> >  [<c02375a6>] debugfs_create_file+0x46/0x210
> >  [<c02377f1>] debugfs_create_dir+0x21/0x30
> >  [<f8901f6d>] ieee80211_sta_debugfs_add+0x2d/0x150 [mac80211]
> >  [<f88eba89>] sta_info_debugfs_add_work+0x89/0x130 [mac80211]
> >  [<f890a170>] ? rate_control_pid_add_sta_debugfs+0x0/0x30 [mac80211]

I wonder if there were two separate problems here.  I looked into
this with some detail yesterday and agree with Johannes that the above 
trace is on locking the parent directory's i_mutex, but I too couldn't
see any problems with sta_info_debugfs_add_work.  Other stuff could also 
modify the directory with or without rtnl_lock, but not in a way that 
to my untrained eyes would lead to deadlock.

Or is the trace just wrong?

-- 
Bob Copeland %% www.bobcopeland.com

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/