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 being cached twice,
>> which results in the leaking of a reference and a BUG() on umount.
>>
>> This patch refactors get_xa_root(), __get_xa_root(), and
>> create_xa_root(), into one get_xa_root() function that takes
>> the appropriate locking around the entire critical section.
>
> Great, thanks.
>
> Now we need to work out the timing. Our options are to shove
> it into 2.6.21 immediately, or to give it a run in 2.6.22-rc1 then
> backport into 2.6.21.x.
>
> What is everyone's confidence level?
>
Tested the patch and I confirm that it fixes the problem. Regarding the
confidence level, in my case I can say that on a suse 10.0 I can always
reproduce the bug on every shutdown. Anyway, I'm not using the default
kernel shipped with suse 10.0, but maybe the same bug could be seen in
opensuse 10.3 that (if I'm not wrong) uses a 2.6.20.
BTW there are not enough details, but a similar problem seems to be
already reported here: https://bugzilla.novell.com/show_bug.cgi?id=259215
-Andrea
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
