mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dean Roehrich <roehrich@sgi.com>
To: Luka Renko <luka.renko@hermes.si>
Cc: Nathan Scott <nathans@sgi.com>,
	Linus Torvalds <torvalds@transmeta.com>,
	Andreas Gruenbacher <ag@bestbits.at>,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	acl-devel@bestbits.at, linux-xfs@hermes.si
Subject: Re: [RFC][PATCH] extended attributes
Date: Thu, 08 Nov 2001 10:47:05 -0600	[thread overview]
Message-ID: <200111081647.KAA23811@slobber.americas.sgi.com> (raw)


>From:  Luka Renko <luka.renko@hermes.si>
>I am also thinking in terms of HSM application (or DMAPI if you want). Where
>do you want HSM attributes to be placed? I thought it should be in trusted,
>because we might need access to them from user space. Other option is system
>(that would require accessing them from kernel code) or user (might be
>problematic, since regular user with write permission might remove them...
>Actually, where are XFS guys storing DMAPI attributes today?

On XFS the DMAPI event mask for that file is kept in a field in the
xfs_dinode_core_t structure--so it's in the inode.  On Irix, HSM's store state
info in an extended attribute in the "root" namespace on each file, but they
do it via the appropriate DMAPI calls (which jump to XFS's extended attribute
code) rather than via the extended attribute library.


Dean

             reply	other threads:[~2001-11-08 16:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-08 16:47 Dean Roehrich [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-11-10  9:08 Tim R.
2001-11-11 10:50 ` Nathan Scott
2001-11-12  1:57 ` Anton Altaparmakov
2001-11-12  3:20   ` Nathan Scott
2001-11-08 16:12 Luka Renko
2001-11-08 16:29 ` Andreas Gruenbacher
2001-11-07  0:12 Nathan Scott
2001-11-07  0:23 ` Nathan Scott
2001-11-07  1:32 ` Andi Kleen
2001-11-07  1:38   ` Alexander Viro
2001-11-07  3:19   ` Nathan Scott
2001-11-08  6:48     ` Andi Kleen
2001-11-12  5:01   ` Nathan Scott

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=200111081647.KAA23811@slobber.americas.sgi.com \
    --to=roehrich@sgi.com \
    --cc=acl-devel@bestbits.at \
    --cc=ag@bestbits.at \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@hermes.si \
    --cc=luka.renko@hermes.si \
    --cc=nathans@sgi.com \
    --cc=torvalds@transmeta.com \
    /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

all inboxes | Powered by JetHome®