linux-ext4 - Re: Sync does not flush to disk!?

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 for Android: free password hash cracker in your pocket

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

Message-id: <4FD204B0.3000204@shiftmail.org>
Date:	Fri, 08 Jun 2012 15:57:04 +0200
From:	Asdo <asdo@...ftmail.org>
To:	Phil Turmel <philip@...mel.org>
Cc:	NeilBrown <neilb@...e.de>, linux-raid <linux-raid@...r.kernel.org>,
	linux-ext4@...r.kernel.org
Subject: Re: Sync does not flush to disk!?

On 06/08/12 15:49, Phil Turmel wrote:
>
> To put it another way:  You can't safely access ext filesystems via
> raw devices in two systems.  The kernel cache won't be synchronized,
> and you almost certainly *will* corrupt the contents.

Thanks both of you for your explanations

I might say that it seems to me a bad design: never before I saw a cache 
that is not updated by writes.
Here the cache content is *older* than the data on the real devices!?
if it was *newer*, there are known cases (writeback cache not flushed 
yet), but *older*... never seen.

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