From: Joel Becker <Joel.Becker@oracle.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Sunil Mushran <sunil.mushran@oracle.com>,
tytso@mit.edu, linux-ext4@vger.kernel.org,
Mark Fasheh <mfasheh@suse.com>
Subject: Re: e4defrag and immutable files
Date: Tue, 8 Jun 2010 18:10:28 -0700 [thread overview]
Message-ID: <20100609011028.GD6795@mail.oracle.com> (raw)
In-Reply-To: <4C0EC034.6010603@zytor.com>
On Tue, Jun 08, 2010 at 03:12:04PM -0700, H. Peter Anvin wrote:
> On 06/02/2010 11:02 AM, Sunil Mushran wrote:
> > "Immutable" means the contents do not change. But the file mappings
> > could change.
> >
> > "Fixed mapping" means the mappings do not change but contents
> > could (as long as the ondisk mappings don't).
> >
> > "Fixed metadata" means the entire inode (mappings included) cannot
> > change but the contents could (as long as the ondisk mappings don't).
> > (This does have the side effect of allowing writes without touching the
> > mtime. Like XFS' invisible i/o.)
> >
>
> Actually, if you're going to have three flags you might as well make
> them orthogonal. That is, separate "fixed contents", "fixed mappings",
> "fixed metadata" -- and don't consider the mapping as metadata for this
> purpose.
I think Sunil was defining terms, not suggesting three flags ;-)
That said, it does allow all the possible characteristics in the
discussion. The only ugly think I can see is that we'll have three new
flags, plus the old immutable flag that means the same as setting all
three new flags.
Joel
--
"But all my words come back to me
In shades of mediocrity.
Like emptiness in harmony
I need someone to comfort me."
Joel Becker
Principal Software Developer
Oracle
E-mail: joel.becker@oracle.com
Phone: (650) 506-8127
next prev parent reply other threads:[~2010-06-09 1:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-28 20:14 e4defrag and immutable files H. Peter Anvin
2010-05-28 21:21 ` Greg Freemyer
2010-05-28 22:06 ` H. Peter Anvin
2010-06-01 19:12 ` Eric Sandeen
2010-06-01 19:32 ` Sunil Mushran
2010-06-01 19:49 ` tytso
2010-06-01 20:14 ` Greg Freemyer
2010-06-01 21:00 ` Eric Sandeen
2010-06-01 21:28 ` Sunil Mushran
2010-06-01 22:26 ` tytso
2010-06-01 22:51 ` Sunil Mushran
2010-06-02 7:28 ` H. Peter Anvin
2010-06-02 18:02 ` Sunil Mushran
2010-06-08 22:12 ` H. Peter Anvin
2010-06-09 1:10 ` Joel Becker [this message]
2010-06-09 1:44 ` tytso
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=20100609011028.GD6795@mail.oracle.com \
--to=joel.becker@oracle.com \
--cc=hpa@zytor.com \
--cc=linux-ext4@vger.kernel.org \
--cc=mfasheh@suse.com \
--cc=sunil.mushran@oracle.com \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.