Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759543AbYAVAzW (ORCPT ); Mon, 21 Jan 2008 19:55:22 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753129AbYAVAzJ (ORCPT ); Mon, 21 Jan 2008 19:55:09 -0500 Received: from wx-out-0506.google.com ([66.249.82.225]:18925 "EHLO wx-out-0506.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752203AbYAVAzG (ORCPT ); Mon, 21 Jan 2008 19:55:06 -0500 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=OmVk7bGyTVyQqcB1timnqrYyR66kc4fhrOEWAsnt/dm3BE2dqPMw5qd+hLQ8ssgsGUEc07dXYz0K626m59QInSzJF2MfE7soGg1qS2YRzmhe/uAia1rIB7w1f/44ZpiS5/bLPPdslDS7TZX5tXxsooBrrw60tH1g6o0hocc7lJ8= Message-ID: Date: Tue, 22 Jan 2008 08:55:05 +0800 From: "Dave Young" To: "Jarek Poplawski" Subject: Re: [PATCH 7/7] driver-core : convert semaphore to mutex in struct class Cc: "Kay Sievers" , "Alan Stern" , "Greg KH" , stefanr@s5r6.in-berlin.de, "David Brownell" , "Kernel development list" In-Reply-To: <20080121211625.GA2758@ami.dom.local> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080121211625.GA2758@ami.dom.local> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3370 Lines: 82 On Jan 22, 2008 5:16 AM, Jarek Poplawski wrote: > Dave Young wrote, On 01/21/2008 09:44 AM: > ... > > I applied it in my kernel, built and run without warnings, but it need > > more testing. > > I will be very glad to see the test result about this if you could, thanks. > > Bad news. (Alas I won't be able to check this today.) Hi, thanks your effort. Now I think we should stop this thread and waiting the class_device going away :) Hope the iteration patches 1-6/7 could be applied. > > ============================================= > [ INFO: possible recursive locking detected ] > 2.6.24-rc8 #5 > --------------------------------------------- > modprobe/536 is trying to acquire lock: > (&cls->mutex/1){--..}, at: [] class_device_add+0x2c6/0x322 > > but task is already holding lock: > (&cls->mutex/1){--..}, at: [] class_device_add+0x2c6/0x322 > > other info that might help us debug this: > 2 locks held by modprobe/536: > #0: (&shost->scan_mutex){--..}, at: [] __scsi_add_device+0x60/0xc9 [scsi_mod] > #1: (&cls->mutex/1){--..}, at: [] class_device_add+0x2c6/0x322 > > stack backtrace: > Pid: 536, comm: modprobe Not tainted 2.6.24-rc8 #5 > [] __lock_acquire+0x962/0x10d4 > [] _spin_unlock_irqrestore+0x34/0x39 > [] kfree+0x87/0xad > [] trace_hardirqs_on+0xba/0x15b > [] lock_acquire+0x71/0x8b > [] class_device_add+0x2c6/0x322 > [] mutex_lock_nested+0x92/0x2bc > [] class_device_add+0x2c6/0x322 > [] class_device_add+0x2c6/0x322 > [] class_device_add+0x2c6/0x322 > [] kobject_get+0xf/0x13 > [] kobject_init+0x29/0x38 > [] class_device_create+0x7d/0x9e > [] sg_add+0x144/0x39f [sg] > [] class_device_add+0x2f4/0x322 > [] scsi_sysfs_add_sdev+0x64/0x1ac [scsi_mod] > [] ata_scsi_dev_config+0x14/0x91 [libata] > [] scsi_probe_and_add_lun+0x9c0/0x9e0 [scsi_mod] > [] __scsi_add_device+0x60/0xc9 [scsi_mod] > [] __scsi_add_device+0xc7/0xc9 [scsi_mod] > [] ata_scsi_scan_host+0xd3/0x26a [libata] > [] ata_host_register+0x205/0x280 [libata] > [] ata_interrupt+0x0/0x200 [libata] > [] ata_host_activate+0x8b/0xf2 [libata] > [] svia_init_one+0x2e2/0x511 [sata_via] > [] pci_match_device+0xa5/0xb6 > [] svia_init_one+0x0/0x511 [sata_via] > [] pci_device_probe+0x40/0x5f > [] driver_probe_device+0x7c/0x175 > [] __driver_attach+0xa2/0xa4 > [] bus_for_each_dev+0x3c/0x5a > [] driver_attach+0x16/0x1a > [] __driver_attach+0x0/0xa4 > [] bus_add_driver+0x72/0x1c0 > [] __pci_register_driver+0x56/0x89 > [] sys_init_module+0xf8/0x1891 > [] ata_port_start+0x0/0x65 [libata] > [] trace_hardirqs_on+0xba/0x15b > [] syscall_call+0x7/0xb > ======================= > scsi 2:0:0:0: Attached scsi generic sg1 type 0 > > Regards, > Jarek P. > -- 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/