[lkml]   [2003]   [Feb]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] Extended attribute fixes, etc.
Andreas Gruenbacher <> wrote:
> Hi Andrew,
> here are five patches against 2.5.60. Each file contains a brief
> description of what it does.

Minor point:

> int
> ext3_xattr_set(struct inode *inode, int name_index, const char *name,
> const void *value, size_t value_len, int flags)
> {
> handle_t *handle;
> int error;
> lock_kernel();
> handle = ext3_journal_start(inode, EXT3_XATTR_TRANS_BLOCKS);
> if (IS_ERR(handle))
> error = PTR_ERR(handle);
> else
> error = ext3_xattr_set_handle(handle, inode, name_index, name,
> value, value_len, flags);
> ext3_journal_stop(handle, inode);

ext3_journal_stop() can return an error code - most notable -EIO if it was a
synchronous transaction, or the filesystem has detected corruption.

> The third to fifth are all steps towards trusted extended attributes,
> which are useful for privileged processes (mostly daemons). One use for
> this is Hierarchical Storage Management, in which a user space daemon
> stores online/offline information for files in trusted EA's, and the
> kernel communicates requests to bring files online to that daemon. This
> class of EA's will also find its way into XFS and ReiserFS, and
> expectedly also into JFS in this form. (Trusted EAs are included in the
> 2.4.19/2.4.20 patches as well.)

So is this new code actually functional yet? As in: something in-kernel
using it?

If not, what is involved in completing the kernel side of trusted EA's?

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:33    [W:0.067 / U:3.040 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site