Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1764071AbYHFBwZ (ORCPT ); Tue, 5 Aug 2008 21:52:25 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755416AbYHFBvT (ORCPT ); Tue, 5 Aug 2008 21:51:19 -0400 Received: from ti-out-0910.google.com ([209.85.142.188]:56632 "EHLO ti-out-0910.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751567AbYHFBvQ (ORCPT ); Tue, 5 Aug 2008 21:51:16 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=xsKDVtU+5aIMERyk3E7qntrxrgID9D/3wptZEMicEpE+k1e8jCFej8+x6WIV3XBlR9 Msa813uzQz+WoZfX7R1rcTOY1LPRL9VVdfhZ/DURbOn3rVb5gnhMdjKL50+9Gehrshht tycSXovOKLx0753L3zvOMKabOGrL+s/F14Tsg= Message-ID: Date: Wed, 6 Aug 2008 09:51:14 +0800 From: "Dave Young" To: "Bob Copeland" Subject: Re: [BUG] wireless : cpu stuck for 61s Cc: "Jiri Slaby" , "Pekka J Enberg" , "Andrew Morton" , "Johannes Berg" , linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org In-Reply-To: <20080805122408.GA5000@hash.localnet> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080729055731.GA3265@darkstar> <1217334724.10489.47.camel@johannes.berg> <20080730020820.8bcc00e2.akpm@linux-foundation.org> <20080730031047.54e13e2d.akpm@linux-foundation.org> <4896D34A.1000005@gmail.com> <20080805122408.GA5000@hash.localnet> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1564 Lines: 43 On Tue, Aug 5, 2008 at 8:24 PM, Bob Copeland wrote: > 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. >> >> > [] ? debugfs_create_file+0x46/0x210 >> > [] ? debugfs_create_file+0x46/0x210 >> > [] debugfs_create_file+0x46/0x210 >> > [] debugfs_create_dir+0x21/0x30 >> > [] ieee80211_sta_debugfs_add+0x2d/0x150 [mac80211] >> > [] sta_info_debugfs_add_work+0x89/0x130 [mac80211] >> > [] ? 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. Yes,. I think so. It's the original bug for me, while testing I found the mutex deadlock problem. But this week I will have no time to trace it. so if I have time I will keep tracing the problem > > Or is the trace just wrong? > > -- > Bob Copeland %% www.bobcopeland.com > > -- Regards dave -- 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/