Re: BUG? a suspected race bug at ext3_xattr_block_set()

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



  Hi,

> I am reporting a suspected data race bug from ext3/xattr.c in Linux 2.6.31.
  Thank you for your report.

> In ext3_xattr_block_set(), it accesses bs->bh->b_data
> while it does not hold lock_buffer(bs->bh).
> 
> However, there is no lock_buffer(bs->bh) and unlock_buffer(bs->bh)
> for guarding the access (at line 794).
  Yes, but we don't really look at the content of bs->bh->b_data. We
just compare the pointers and for that we definitely don't need the
lock. So I don't see problem. If you still do, please tell me more
details (like a sample of code executions of two threads which race).
Thanks.

								Honza
-- 
Jan Kara <jack@xxxxxxx>
SuSE CR Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Reiser Filesystem Development]     [Ceph FS]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux FS]     [Yosemite National Park]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Device Mapper]     [Linux Media]

  Powered by Linux