Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932149AbZDGV5q (ORCPT ); Tue, 7 Apr 2009 17:57:46 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756729AbZDGV53 (ORCPT ); Tue, 7 Apr 2009 17:57:29 -0400 Received: from mail-fx0-f158.google.com ([209.85.220.158]:37674 "EHLO mail-fx0-f158.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1761383AbZDGV50 (ORCPT ); Tue, 7 Apr 2009 17:57:26 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=xcv2UAxeMqe/oa4QNW7F9MVTYOlNy6iI/XFBU+WutcvYRG5dwr/6oHUYC+DoymmO+p JrmuFaJEiS6UlT6A0to16saqpI3CstZH8Udij8lHPYrD+Eph1r5CdvJpTcebHFNgRb7H tDXNFGGd0Op/TCUJAkg1otQTmmDLlcM1afJv8= Date: Tue, 7 Apr 2009 23:57:22 +0200 From: Frederic Weisbecker To: Alexander Beregalov Cc: LKML , Jeff Mahoney , Peter Zijlstra , ReiserFS Development List , Bron Gondwana , Andrew Morton , Linus Torvalds , Ingo Molnar , Alexander Viro Subject: Re: [PATCH] reiserfs: kill-the-BKL Message-ID: <20090407215721.GA6252@nowhere> References: <1239070789-13354-1-git-send-email-fweisbec@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 5709 Lines: 146 On Wed, Apr 08, 2009 at 01:34:07AM +0400, Alexander Beregalov wrote: > Hi Frederic > > I've applied your patch. > This is UP system. > This warning seems related to your patch. > > > [ INFO: possible circular locking dependency detected ] > 2.6.29-10247-g8e2c4f2-dirty #2 > ------------------------------------------------------- > udevadm/1239 is trying to acquire lock: > (&mm->mmap_sem){++++++}, at: [] might_fault+0x52/0xa0 > > but task is already holding lock: > (sysfs_mutex){+.+.+.}, at: [] sysfs_readdir+0x56/0x200 Ah, I've never hit it. I'm not sure this is related to my patch but it could be. Could you send me your config? Thanks, Frederic. > > which lock already depends on the new lock. > > > the existing dependency chain (in reverse order) is: > > -> #3 (sysfs_mutex){+.+.+.}: > [] __lock_acquire+0xd1a/0x1160 > [] lock_acquire+0x74/0x90 > [] __mutex_lock_common+0x50/0x430 > [] mutex_lock_nested+0x33/0x40 > [] sysfs_addrm_start+0x2c/0xc0 > [] create_dir+0x40/0x80 > [] sysfs_create_dir+0x2b/0x50 > [] kobject_add_internal+0xc1/0x220 > [] kobject_add_varg+0x31/0x50 > [] kobject_add+0x2c/0x60 > [] device_add+0xe2/0x540 > [] add_partition+0x112/0x210 > [] rescan_partitions+0x23f/0x320 > [] __blkdev_get+0x153/0x330 > [] blkdev_get+0xa/0x10 > [] register_disk+0x10a/0x130 > [] add_disk+0x109/0x170 > [] sd_probe_async+0x19a/0x280 > [] async_thread+0xd0/0x230 > [] kthread+0x3a/0x70 > [] kernel_thread_helper+0x7/0x10 > [] 0xffffffff > > -> #2 (&bdev->bd_mutex){+.+.+.}: > [] __lock_acquire+0xd1a/0x1160 > [] lock_acquire+0x74/0x90 > [] __mutex_lock_common+0x50/0x430 > [] mutex_lock_nested+0x33/0x40 > [] __blkdev_get+0x33/0x330 > [] blkdev_get+0xa/0x10 > [] open_by_devnum+0x21/0x50 > [] journal_init+0x22e/0x19a0 > [] reiserfs_fill_super+0x3a1/0x1050 > [] get_sb_bdev+0x133/0x160 > [] get_super_block+0x21/0x30 > [] vfs_kern_mount+0x3a/0xa0 > [] do_kern_mount+0x39/0xd0 > [] do_mount+0x3a3/0x790 > [] sys_mount+0x89/0xc0 > [] mount_block_root+0xd0/0x261 > [] mount_root+0x59/0x5f > [] prepare_namespace+0xef/0x171 > [] kernel_init+0xd5/0xee > [] kernel_thread_helper+0x7/0x10 > [] 0xffffffff > > -> #1 (&REISERFS_SB(s)->lock){+.+.+.}: > [] __lock_acquire+0xd1a/0x1160 > [] lock_acquire+0x74/0x90 > [] __mutex_lock_common+0x50/0x430 > [] mutex_lock_nested+0x33/0x40 > [] reiserfs_write_lock+0x1e/0x30 > [] reiserfs_get_block+0x66/0x14f0 > [] do_mpage_readpage+0x340/0x490 > [] mpage_readpages+0x9e/0xe0 > [] reiserfs_readpages+0x19/0x20 > [] __do_page_cache_readahead+0x13f/0x200 > [] do_page_cache_readahead+0x4e/0x70 > [] filemap_fault+0x30f/0x430 > [] __do_fault+0x3d/0x360 > [] handle_mm_fault+0x100/0x590 > [] do_page_fault+0x121/0x280 > [] error_code+0x6a/0x70 > [] load_elf_binary+0x9d0/0x19f0 > [] search_binary_handler+0x163/0x2f0 > [] do_execve+0x21d/0x2b0 > [] sys_execve+0x3e/0x70 > [] syscall_call+0x7/0xb > [] 0xffffffff > > -> #0 (&mm->mmap_sem){++++++}: > [] __lock_acquire+0xdce/0x1160 > [] lock_acquire+0x74/0x90 > [] might_fault+0x83/0xa0 > [] copy_to_user+0x36/0x130 > [] filldir64+0xa4/0xf0 > [] sysfs_readdir+0x116/0x200 > [] vfs_readdir+0x7e/0xa0 > [] sys_getdents64+0x69/0xb0 > [] sysenter_do_call+0x12/0x36 > [] 0xffffffff > > other info that might help us debug this: > > 2 locks held by udevadm/1239: > #0: (&type->i_mutex_dir_key){+.+.+.}, at: [] vfs_readdir+0x4f/0xa0 > #1: (sysfs_mutex){+.+.+.}, at: [] sysfs_readdir+0x56/0x200 > > stack backtrace: > Pid: 1239, comm: udevadm Not tainted 2.6.29-10247-g8e2c4f2-dirty #2 > Call Trace: > [] ? printk+0x18/0x1e > [] print_circular_bug_tail+0x8c/0xe0 > [] __lock_acquire+0xdce/0x1160 > [] ? put_lock_stats+0xd/0x30 > [] lock_acquire+0x74/0x90 > [] ? might_fault+0x52/0xa0 > [] might_fault+0x83/0xa0 > [] ? might_fault+0x52/0xa0 > [] copy_to_user+0x36/0x130 > [] filldir64+0xa4/0xf0 > [] sysfs_readdir+0x116/0x200 > [] ? filldir64+0x0/0xf0 > [] vfs_readdir+0x7e/0xa0 > [] ? filldir64+0x0/0xf0 > [] sys_getdents64+0x69/0xb0 > [] sysenter_do_call+0x12/0x36 -- 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/