From: Alex Tomas <bzzz@sun.com>
Subject: Re: More ext4 acl/xattr corruption - 4th occurence now
Date: Tue, 19 May 2009 19:16:20 +0400
Message-ID: <4A12CD44.1070808@sun.com>
References: <20090514110659.GA5146@kulgan> <20090514132506.GD5146@kulgan>
 <20090514140732.GI11352@mit.edu> <20090514143014.GH5146@kulgan>
 <20090514161254.GJ11352@mit.edu> <20090514210244.GL5146@kulgan>
 <20090514212325.GG21316@mit.edu> <m2iqjx5s4n.fsf@vador.mandriva.com>
 <20090519113644.GA7927@mit.edu> <4A129FA0.9050500@sun.com>
 <20090519150430.GC7927@mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; CHARSET=US-ASCII; format=flowed
Content-Transfer-Encoding: 7BIT
Cc: Thierry Vignaud <tvignaud@mandriva.com>,
	Kevin Shanahan <kmshanah@ucwb.org.au>,
	Andreas Dilger <adilger@sun.com>, linux-ext4@vger.kernel.org
To: Theodore Tso <tytso@mit.edu>
In-reply-to: <20090519150430.GC7927@mit.edu>
Sender: linux-ext4-owner@vger.kernel.org

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