From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759831AbXGPSYL (ORCPT ); Mon, 16 Jul 2007 14:24:11 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751246AbXGPSX6 (ORCPT ); Mon, 16 Jul 2007 14:23:58 -0400 Received: from rv-out-0910.google.com ([209.85.198.185]:51404 "EHLO rv-out-0910.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750881AbXGPSX5 (ORCPT ); Mon, 16 Jul 2007 14:23:57 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:x-enigmail-version:content-type:content-transfer-encoding; b=X39N9rB0zl7VgxQX9c7qaSbd2lNSaZ9HGKpmy7mCRPuJMSNstCUbA3J6zf1Hgcru9dmVaXVCTmr8YXdCq18WWb3uxir4rg5hqZWdf4AqT6YUpZV25qeMFJELPvTZwF34CXyXpeX9PMQJzFXdoYI038yNXAszozvwOg9WXhLBuE4= Message-ID: <469BB7B8.3060002@gmail.com> Date: Tue, 17 Jul 2007 03:23:52 +0900 From: Tejun Heo User-Agent: Icedove 1.5.0.10 (X11/20070307) MIME-Version: 1.0 To: Satyam Sharma CC: Gabriel C , Linux Kernel Mailing List , Christoph Lameter , gregkh@suse.de Subject: Re: Oops while modprobing phy fixed module References: <4698BF14.10807@googlemail.com> <469A5C94.7030201@googlemail.com> <469A9D5D.10509@googlemail.com> <469B61C8.8010902@googlemail.com> In-Reply-To: X-Enigmail-Version: 0.94.2.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Satyam Sharma wrote: > On 7/16/07, Gabriel C wrote: >> Here the bisect result: >> >> 3007e997de91ec59af39a3f9c91595b31ae6e08b is first bad commit >> commit 3007e997de91ec59af39a3f9c91595b31ae6e08b >> Author: Tejun Heo >> Date: Thu Jun 14 04:27:23 2007 +0900 >> >> sysfs: use sysfs_mutex to protect the sysfs_dirent tree Hmmm... Weird. The patch is supposed to make synchronization more strict not less unless I've forgotten locking at some place. Gabriel, can you please choose SLAB and enable CONFIG_DEBUG_SLAB and DEBUG_SLAB_LEAK and see whether kernel complains about something? Thanks. -- tejun