-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
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
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 end up
-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
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,
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
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
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,
8 matches
Mail list logo