From: Chris Mason <mason@suse.com>
To: Russell Coker <russell@coker.com.au>
Cc: reiserfs-list@namesys.com
Subject: Re: xattr
Date: 19 Jun 2003 09:52:00 -0400 [thread overview]
Message-ID: <1056030719.6758.97.camel@tiny.suse.com> (raw)
In-Reply-To: <200306162226.39701.russell@coker.com.au>
On Mon, 2003-06-16 at 08:26, Russell Coker wrote:
> What is the status of xattr support in 2.5.x?
>
> How is journalling of xattr's being handled?
>
> For correct operation of SE Linux we need to have the xattr that is used for
> the security context be changed atomically, and if a file is created and
> immediately has the xattr set then ideally we would have the file creation
> and the xattr creation in the same journal entry.
>
> Is this possible? If doing this requires that the file system be mounted with
> data=journal then this will be fine.
How big are the xattrs you have in mind? We can get atomic writes of 4k
in length but beyond that things get more difficult.
As for the xattr and the create in the same transaction, that's a little
harder. We'd probably need a new syscall, or to change the semantics of
the xattr call such that creating an xattr on a file that doesn't exist
also creates the file.
-chris
next prev parent reply other threads:[~2003-06-19 13:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-16 12:26 xattr Russell Coker
2003-06-17 11:04 ` xattr Hans Reiser
2003-06-19 13:52 ` Chris Mason [this message]
2003-06-19 14:46 ` xattr Russell Coker
2003-06-19 14:55 ` xattr Chris Mason
2003-06-19 15:12 ` xattr Russell Coker
2003-06-19 15:10 ` xattr Stephen Smalley
2003-06-19 15:21 ` xattr Chris Mason
2003-06-19 17:25 ` xattr Stephen Smalley
2003-06-19 18:06 ` xattr Chris Mason
2003-06-19 18:52 ` xattr Stephen Smalley
2003-06-19 18:55 ` how to fix the file system which has a dangling file? bmoon
2003-06-23 7:56 ` xattr Hans Reiser
[not found] <200312021433.48383.russell@coker.com.au>
2003-12-02 14:45 ` xattr James Carter
2003-12-02 14:45 ` xattr James Carter
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=1056030719.6758.97.camel@tiny.suse.com \
--to=mason@suse.com \
--cc=reiserfs-list@namesys.com \
--cc=russell@coker.com.au \
/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.