linux-kernel - Re: 2.6.20-mm2: possible recursive locking detected (reiserfs-related)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200702202223.54046.rjw@sisk.pl>
Date:	Tue, 20 Feb 2007 22:23:53 +0100
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: 2.6.20-mm2: possible recursive locking detected (reiserfs-related)

On Sunday, 18 February 2007 06:51, Andrew Morton wrote:
> 
> Temporarily at
> 
>   http://userweb.kernel.org/~akpm/2.6.20-mm2/
> 
> Will appear later at
> 
>  ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.20/2.6.20-mm2/

Looks like reiserfs has some locking problems:

=============================================
[ INFO: possible recursive locking detected ]
2.6.20-mm2 #6
---------------------------------------------
beagled/4786 is trying to acquire lock:
 (&inode->i_mutex){--..}, at: [<ffffffff80479df9>] mutex_lock+0x19/0x20

but task is already holding lock:
 (&inode->i_mutex){--..}, at: [<ffffffff80479df9>] mutex_lock+0x19/0x20

other info that might help us debug this:
3 locks held by beagled/4786:
 #0:  (&inode->i_mutex){--..}, at: [<ffffffff80479df9>] mutex_lock+0x19/0x20
 #1:  (&REISERFS_I(inode)->xattr_sem){----}, at: [<ffffffff80304c99>] reiserfs_setxattr+0x79/0x150
 #2:  (&REISERFS_SB(s)->xattr_dir_sem){----}, at: [<ffffffff80304cc0>] reiserfs_setxattr+0xa0/0x150

stack backtrace:

Call Trace:
 [<ffffffff8024823f>] __lock_acquire+0xa9f/0xf30
 [<ffffffff80479df9>] mutex_lock+0x19/0x20
 [<ffffffff80248758>] lock_acquire+0x88/0xc0
 [<ffffffff80479df9>] mutex_lock+0x19/0x20
 [<ffffffff80479c5c>] __mutex_lock_slowpath+0xec/0x270
 [<ffffffff8028d63a>] dentry_open+0x6a/0x80
 [<ffffffff80479df9>] mutex_lock+0x19/0x20
 [<ffffffff803052c7>] reiserfs_xattr_set+0x127/0x3d0
 [<ffffffff80246ffd>] mark_held_locks+0x5d/0x90
 [<ffffffff8047add8>] __down_write_nested+0x38/0xb0
 [<ffffffff8024722f>] trace_hardirqs_on+0x13f/0x170
 [<ffffffff8047b96b>] _spin_unlock_irq+0x2b/0x40
 [<ffffffff80305698>] user_set+0x68/0x90
 [<ffffffff80304cd4>] reiserfs_setxattr+0xb4/0x150
 [<ffffffff802ad829>] vfs_setxattr+0xb9/0x200
 [<ffffffff802ada5a>] setxattr+0xea/0x110
 [<ffffffff8024722f>] trace_hardirqs_on+0x13f/0x170
 [<ffffffff8028a342>] poison_obj+0x42/0x60
 [<ffffffff8028aa75>] kmem_cache_free+0xf5/0x110
 [<ffffffff8024722f>] trace_hardirqs_on+0x13f/0x170
 [<ffffffff80298aef>] putname+0x3f/0x50
 [<ffffffff8029ac67>] __user_walk_fd+0x57/0x70
 [<ffffffff802adae3>] sys_lsetxattr+0x63/0x90
 [<ffffffff8047b020>] trace_hardirqs_on_thunk+0x35/0x37
 [<ffffffff8024722f>] trace_hardirqs_on+0x13f/0x170
 [<ffffffff8047b020>] trace_hardirqs_on_thunk+0x35/0x37
 [<ffffffff8020989e>] system_call+0x7e/0x83
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/