Re: [PATCH] reiserfs: fix xattr root locking/refcount bug

2007-04-22 Thread Jeff Mahoney
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andrew Morton wrote: > On Sat, 21 Apr 2007 11:26:31 -0400 Jeff Mahoney <[EMAIL PROTECTED]> wrote: > >> The listxattr() and getxattr() operations are only protected by a read >> lock. As a result, if either of these operations run in parallel, a race

Re: [PATCH] reiserfs: fix xattr root locking/refcount bug

2007-04-22 Thread Andrea Righi
Andrew Morton wrote: > On Sat, 21 Apr 2007 11:26:31 -0400 Jeff Mahoney <[EMAIL PROTECTED]> wrote: > >> The listxattr() and getxattr() operations are only protected by a read >> lock. As a result, if either of these operations run in parallel, a race >> condition exists where the xattr_root will

Re: [PATCH] reiserfs: fix xattr root locking/refcount bug

2007-04-21 Thread Andrew Morton
On Sat, 21 Apr 2007 11:26:31 -0400 Jeff Mahoney <[EMAIL PROTECTED]> wrote: > The listxattr() and getxattr() operations are only protected by a read > lock. As a result, if either of these operations run in parallel, a race > condition exists where the xattr_root will end up being cached twice,

[PATCH] reiserfs: fix xattr root locking/refcount bug

2007-04-21 Thread Jeff Mahoney
The listxattr() and getxattr() operations are only protected by a read lock. As a result, if either of these operations run in parallel, a race condition exists where the xattr_root will end up being cached twice, which results in the leaking of a reference and a BUG() on umount. This patch r