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-next>] [day] [month] [year] [list]
Message-Id: <20081106185109.ce8be9b8.akpm@linux-foundation.org>
Date:	Thu, 6 Nov 2008 18:51:09 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	=?UTF-8?Q? "=ED=99=8D=EC=8B=A0_shin_hong" ?= <hongshin@...il.com>
Cc:	adilger@....com, linux-ext4@...r.kernel.org
Subject: Re: a suspected data race bug in Ext4 file system

On Fri, 7 Nov 2008 11:09:49 +0900 "______ shin hong" <hongshin@...il.com> wrote:

> Dear Ext4 maintainer,
> 
> I found a suspected data race bug at ext4_release_file() in ext4/file.c .
> 
> Is it necessary to re-check whether the if-statement's
> condition(atomic_read(&inode->i_writecount) == 1) is satisifed after
> semaphore down operation?
> 
> It seems to use "test and test and set" pattern(double-checking)
>  but the second "test" seems to be missed.
> 
> Please examine this function. Thank you.
> 
> p.s. I sent the same report to sct@...hat.com. But I did not received
> any reply.
>        I think my mail was discarded so I am sending the same again.
> 

An appropriate way to report this possible bug is to Cc: the ext4 mailing
list, which I have cc'ed here.

Thanks.
--
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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ