linux-ext4 - Re: [PATCH] [RFC] New fsck option to ignore device-mapper crypto devices

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: <20080306174220.GH18188@mit.edu>
Date:	Thu, 6 Mar 2008 12:42:20 -0500
From:	Theodore Tso <tytso@....EDU>
To:	Dave Kleikamp <shaggy@...ux.vnet.ibm.com>
Cc:	Matthias Koenig <mkoenig@...e.de>, ludwig.nussel@...e.de,
	linux-ext4@...r.kernel.org
Subject: Re: [PATCH] [RFC] New fsck option to ignore device-mapper crypto
	devices

On Thu, Mar 06, 2008 at 11:23:47AM -0600, Dave Kleikamp wrote:
> Zero tells fsck not to check the filesystem during reboot.  It's what
> tells fsck -A which filesystems to check.  If we don't expect the
> filesystem to be check-able during that phase, a non-zero value won't
> have any real meaning.

I'm now beginning to understand why SuSE wanted fsck -M/-m (ignore
mounted filesystems).  Looks like SuSE has a very strange and
non-standard usage scenario with fsck -A which is *not* just at
boot-time.

So before we try to figure out whether Yet Another FSCK option makes
sense, maybe it would be good to get an explanation exactly *how* SuSE
is using fsck -A, besides just at boot-time?

						- 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