linux-ext4 - Re: BUG? a suspected race bug at ext3_xattr_block

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Thu, 10 Dec 2009 16:42:03 +0100
From:	Jan Kara <jack@...e.cz>
To:	홍신 shin hong <hongshin@...il.com>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: BUG? a suspected race bug at ext3_xattr_block_set()

  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@...e.cz>
SuSE CR Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html