public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Gruenbacher <agruen@suse.de>
To: "Stephen C. Tweedie" <sct@redhat.com>
Cc: Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>,
	Andrew Tridgell <tridge@osdl.org>,
	Andreas Dilger <adilger@clusterfs.com>,
	Alex Tomas <alex@clusterfs.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Fix ea-in-inode default ACL creation
Date: Fri, 21 Jan 2005 22:48:41 +0100	[thread overview]
Message-ID: <1106344121.19651.55.camel@winden.suse.de> (raw)
In-Reply-To: <1106343376.1989.437.camel@sisko.sctweedie.blueyonder.co.uk>

On Fri, 2005-01-21 at 22:36, Stephen C. Tweedie wrote:
> Ugh.  It feels horrible to have to do this, but we _do_ want to clear
> the raw inode, and we only want to do it once, and we have to do it on
> first access to the on-disk structures.  I can't see an easy way round
> it that doesn't add more overhead.

Well, we could split EXT3_STATE_NEW into a "GOOD_OLD_NEW" flag for the
first 128 bytes and a "BIG_INODE_NEW" flag for the rest, and only
initialize the rest in the xattr code when necessary. Not any better it
I suppose. Note that this change has no effect except with default ACLs
anyway.

-- Andreas.


  reply	other threads:[~2005-01-21 22:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-20 18:22 Fix ea-in-inode default ACL creation Andreas Gruenbacher
2005-01-20 18:56 ` Valdis.Kletnieks
2005-01-20 19:07   ` Andreas Dilger
2005-01-20 19:09   ` Andreas Gruenbacher
2005-01-20 19:21     ` Valdis.Kletnieks
2005-01-21 21:36 ` Stephen C. Tweedie
2005-01-21 21:48   ` Andreas Gruenbacher [this message]
2005-01-21 22:06     ` Stephen C. Tweedie

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=1106344121.19651.55.camel@winden.suse.de \
    --to=agruen@suse.de \
    --cc=adilger@clusterfs.com \
    --cc=akpm@osdl.org \
    --cc=alex@clusterfs.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sct@redhat.com \
    --cc=torvalds@osdl.org \
    --cc=tridge@osdl.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