linux-ext4 - Re: More ext4 acl/xattr corruption

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] [thread-next>] [day] [month] [year] [list]

Message-id: <4A12CD44.1070808@sun.com>
Date:	Tue, 19 May 2009 19:16:20 +0400
From:	Alex Tomas <bzzz@....com>
To:	Theodore Tso <tytso@....edu>
Cc:	Thierry Vignaud <tvignaud@...driva.com>,
	Kevin Shanahan <kmshanah@...b.org.au>,
	Andreas Dilger <adilger@....com>, linux-ext4@...r.kernel.org
Subject: Re: More ext4 acl/xattr corruption - 4th occurence now

Theodore Tso wrote:
> On Tue, May 19, 2009 at 04:01:36PM +0400, Alex Tomas wrote:
>> Theodore Tso wrote:
>>> On the other hand, most of the time writes into the directory will
>>> tend to be into pre-existing free space; but if you had two parallel
>>> cp's copying a large number of files into the same directory, that
>>> could certainly happen.
>> isn't access to a directory protected with i_mutex ?
> 
> Hmm, good point.  Yes, that should prevent problems with directories.
> So there should only be a problem when two processes are writing to
> the same file at the same time.

I guess reading can corrupt it as well ?

thanks, Alex
--
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