https://bugzilla.novell.com/show_bug.cgi?id=336669#c32
--- Comment #32 from Jeff Mahoney 2007-11-02 10:47:26 MST ---
Created an attachment (id=181839)
--> (https://bugzilla.novell.com/attachment.cgi?id=181839)
[PATCH] reiserfs: bad unlock in reiserfs_xattr_get
WARNING: at kernel/mutex-debug.c:82 debug_mutex_unlock()
Call Trace:
[<ffffffff80249c32>] debug_mutex_unlock+0x5e/0x132
[<ffffffff8041592d>] __mutex_unlock_slowpath+0xba/0xfd
[<ffffffff880ba3d1>] :reiserfs:reiserfs_xattr_get+0x234/0x24f
[<ffffffff80294cc5>] do_lookup+0x63/0x1ae
[<ffffffff880ba01b>] :reiserfs:reiserfs_getxattr+0x7b/0xa2
[<ffffffff802a799d>] vfs_getxattr+0x96/0xf5
[<ffffffff802a7aa2>] getxattr+0xa6/0x105
[<ffffffff80287362>] poison_obj+0x26/0x2f
[<ffffffff8028767f>] cache_free_debugcheck+0x18d/0x19c
[<ffffffff802a7b4c>] sys_lgetxattr+0x4b/0x69
[<ffffffff80209d51>] tracesys+0x71/0xe1
[<ffffffff80209dbc>] tracesys+0xdc/0xe1
This is what I was looking for. I've found a bug where if getxattr() is called
with either a NULL buffer (common) or a too small buffer (not common), it
incorrectly unlocks the mutex, despite it not having been locked.
I've checked in a patch to the CVS tree.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.