From: tytso@mit.edu
To: Amir Goldstein <amir73il@gmail.com>
Cc: Andreas Dilger <adilger@dilger.ca>,
Ext4 Developers List <linux-ext4@vger.kernel.org>
Subject: Re: Next3 on-disk format change request
Date: Wed, 23 Jun 2010 20:35:29 -0400 [thread overview]
Message-ID: <20100624003529.GF6843@thunk.org> (raw)
In-Reply-To: <AANLkTikAoKpZNGvtyYscPLVH1HrW3xaCZ84sVc62UGD4@mail.gmail.com>
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
next prev parent reply other threads:[~2010-06-24 0:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-22 10:30 Next3 on-disk format change request Amir Goldstein
2010-06-24 0:35 ` tytso [this message]
2010-06-24 5:33 ` Amir Goldstein
2010-12-21 12:28 ` Amir Goldstein
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100624003529.GF6843@thunk.org \
--to=tytso@mit.edu \
--cc=adilger@dilger.ca \
--cc=amir73il@gmail.com \
--cc=linux-ext4@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).