linux-ext4 - Re: [ext3] Changes to block device after an ext3 mount point has been remounted readonly

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: <16F918FB-F45D-478E-9358-550BB39E277E@sun.com>
Date:	Mon, 22 Feb 2010 16:09:17 -0700
From:	Andreas Dilger <adilger@....com>
To:	Jan Kara <jack@...e.cz>
Cc:	Camille Moncelier <pix@...life.org>, linux-fsdevel@...r.kernel.org,
	ext4 development <linux-ext4@...r.kernel.org>
Subject: Re: [ext3] Changes to block device after an ext3 mount point has	been
 remounted readonly

On 2010-02-22, at 16:05, Jan Kara wrote:
>  Hmm, and apparently there is some subtlety in the loopback device  
> code because even when I use sync(1), the first and second images  
> sometimes differ (although it's much rarer). But I see a commit  
> block of the transaction  already in the first image (the commit  
> block is written last) but the contents of the transaction is  
> present only in the second image.


It has never been safe to run ext3 on top of a loop device, because  
the loop device does not preserve ordering, and I'm not sure whether  
it properly passes barriers either.

Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.

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