linux-kernel - Re: ext3fs: umount+sync not enough to guarantee metadata-on-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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Tue, 12 Jun 2007 16:15:58 +0100
From:	"Stephen C. Tweedie" <sct@...hat.com>
To:	Pavel Machek <pavel@....cz>
Cc:	Mark Lord <lkml@....ca>, Andrew Morton <akpm@...ux-foundation.org>,
	"Theodore Ts'o" <tytso@....edu>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Stephen Tweedie <sct@...hat.com>
Subject: Re: ext3fs: umount+sync not enough to guarantee metadata-on-disk

Hi,

On Sun, 2007-06-10 at 18:27 +0000, Pavel Machek wrote:

> > Once a f/s is read-only, there should be NO writing to 
> > it.  Right?
> 
> Linux happily writes to filesystems mounted read-only. It will replay
> journal on them.

Only at mount time, not on unmount; and it does check whether the
underlying device is truly readonly or not first (assuming
bdev_read_only() is working on the device in question.)

--Stephen


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/