linux-ext4 - Re: [PATCH e2fsprogs] - ignore bind mounts in fsck

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: <20070919204249.GH25497@thunk.org>
Date:	Wed, 19 Sep 2007 16:42:49 -0400
From:	Theodore Tso <tytso@....edu>
To:	Eric Sandeen <sandeen@...hat.com>
Cc:	ext4 development <linux-ext4@...r.kernel.org>
Subject: Re: [PATCH e2fsprogs] - ignore bind mounts in fsck

On Wed, Sep 19, 2007 at 03:20:14PM -0500, Eric Sandeen wrote:
> An entry like this in /etc/fstab:
> 
> /foo	/bar	ext3	bind,defaults	1 3
> 
> will stop boot, as fsck.ext3 tries to check it and fails:
> 
> e2fsck 1.40.2 (12-Jul-2007)
> fsck.ext3: Is a directory while trying to open /foo
> 
> The superblock could not be read or does not describe a correct ext2
> filesystem. ...
> 
> Granted, asking for fsck of a bind mount in the fstab is a bit odd, 
> but it doesn't seem like it should stop the boot process if you make
> this mistake.

That's fair, but note that the dump number and fsck pass number really
should be zero in the fstab entry.  i.e., it really should be "0 0",
or just plain ommitted.

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