linux-ext4 - Re: Next3 on-disk format change request

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: <20100624003529.GF6843@thunk.org>
Date:	Wed, 23 Jun 2010 20:35:29 -0400
From:	tytso@....edu
To:	Amir Goldstein <amir73il@...il.com>
Cc:	Andreas Dilger <adilger@...ger.ca>,
	Ext4 Developers List <linux-ext4@...r.kernel.org>
Subject: Re: Next3 on-disk format change request

On Tue, Jun 22, 2010 at 01:30:54PM +0300, Amir Goldstein wrote:
> My on-disk format change request is to re-assign a ro_compat feature
> for IS_SNAPSHOT (currently in s_flags).

OK, so in addition to:

#define EXT4_FEATURE_RO_COMPAT_HAS_SNAPSHOT	0x0080

You would also like:

#define EXT4_FEATURE_RO_COMPAT_IS_SNAPSHOT	0x0100

which is a feature flag that the kernel will never support, since this
is a hint that snapshot should only be mounted read-only, correct?

						- 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