2015-04-22 06:28:34 +00:00
|
|
|
.\" Extended attributes manual page
|
|
|
|
.\"
|
|
|
|
.\" Copyright (C) 2000, 2002, 2007 Andreas Gruenbacher <agruen@suse.de>
|
|
|
|
.\" Copyright (C) 2001, 2002, 2004, 2007 Silicon Graphics, Inc.
|
|
|
|
.\" All rights reserved.
|
|
|
|
.\"
|
|
|
|
.\" This is free documentation; you can redistribute it and/or
|
|
|
|
.\" modify it under the terms of the GNU General Public License as
|
|
|
|
.\" published by the Free Software Foundation; either version 2 of
|
|
|
|
.\" the License, or (at your option) any later version.
|
|
|
|
.\"
|
|
|
|
.\" The GNU General Public License's references to "object code"
|
|
|
|
.\" and "executables" are to be interpreted as the output of any
|
|
|
|
.\" document formatting or typesetting system, including
|
|
|
|
.\" intermediate and printed output.
|
|
|
|
.\"
|
|
|
|
.\" This manual is distributed in the hope that it will be useful,
|
|
|
|
.\" but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
.\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
|
|
.\" GNU General Public License for more details.
|
|
|
|
.\"
|
|
|
|
.\" You should have received a copy of the GNU General Public
|
|
|
|
.\" License along with this manual. If not, see
|
|
|
|
.\" <http://www.gnu.org/licenses/>.
|
|
|
|
.\"
|
2015-04-22 12:35:54 +00:00
|
|
|
.TH XATTR 7
|
2015-04-22 06:28:34 +00:00
|
|
|
.SH NAME
|
|
|
|
attr - Extended attributes
|
|
|
|
.SH DESCRIPTION
|
|
|
|
Extended attributes are name:value pairs associated permanently with
|
|
|
|
files and directories, similar to the environment strings associated
|
|
|
|
with a process.
|
|
|
|
An attribute may be defined or undefined.
|
|
|
|
If it is defined, its value may be empty or non-empty.
|
|
|
|
.PP
|
|
|
|
Extended attributes are extensions to the normal attributes which are
|
2015-04-22 06:57:02 +00:00
|
|
|
associated with all inodes in the system (i.e., the
|
2015-04-22 06:28:34 +00:00
|
|
|
.BR stat (2)
|
|
|
|
data).
|
|
|
|
They are often used to provide additional functionality
|
2015-04-22 06:59:38 +00:00
|
|
|
to a filesystem\(emfor example, additional security features such as
|
2015-04-22 06:28:34 +00:00
|
|
|
Access Control Lists (ACLs) may be implemented using extended attributes.
|
|
|
|
.PP
|
2015-04-22 12:46:30 +00:00
|
|
|
Users with search access to a file or directory may use
|
|
|
|
.BR listxattr (2)
|
|
|
|
to retrieve a list of attribute names defined for that file or directory.
|
2015-04-22 06:28:34 +00:00
|
|
|
.PP
|
|
|
|
Extended attributes are accessed as atomic objects.
|
2015-04-22 12:46:30 +00:00
|
|
|
Reading
|
|
|
|
.RB ( getxattr (2))
|
|
|
|
retrieves the whole value of an attribute and stores it in a buffer.
|
|
|
|
Writing
|
|
|
|
.RB ( setxattr (2))
|
|
|
|
replaces any previous value with the new value.
|
2015-04-22 06:28:34 +00:00
|
|
|
.PP
|
2015-04-22 11:44:16 +00:00
|
|
|
Space consumed for extended attributes may be counted towards the disk quotas
|
2015-04-22 06:28:34 +00:00
|
|
|
of the file owner and file group.
|
2015-04-22 06:54:38 +00:00
|
|
|
.SS Extended attribute namespaces
|
2015-04-22 07:22:44 +00:00
|
|
|
Attribute names are null-terminated strings.
|
2015-04-22 06:28:34 +00:00
|
|
|
The attribute name is always specified in the fully qualified
|
|
|
|
.IR namespace.attribute
|
2015-04-22 06:57:02 +00:00
|
|
|
form, for example,
|
2015-04-22 06:28:34 +00:00
|
|
|
.IR user.mime_type ,
|
|
|
|
.IR trusted.md5sum ,
|
|
|
|
.IR system.posix_acl_access ,
|
|
|
|
or
|
|
|
|
.IR security.selinux .
|
|
|
|
.PP
|
|
|
|
The namespace mechanism is used to define different classes of extended
|
|
|
|
attributes.
|
2015-04-22 06:57:02 +00:00
|
|
|
These different classes exist for several reasons;
|
|
|
|
for example, the permissions
|
2015-04-22 06:28:34 +00:00
|
|
|
and capabilities required for manipulating extended attributes of one
|
|
|
|
namespace may differ to another.
|
|
|
|
.PP
|
2015-04-22 06:59:38 +00:00
|
|
|
Currently, the
|
2015-04-22 06:28:34 +00:00
|
|
|
.IR security ,
|
|
|
|
.IR system ,
|
|
|
|
.IR trusted ,
|
|
|
|
and
|
|
|
|
.IR user
|
2015-04-22 06:50:55 +00:00
|
|
|
extended attribute classes are defined as described below.
|
|
|
|
Additional classes may be added in the future.
|
2015-04-22 06:28:34 +00:00
|
|
|
.SS Extended security attributes
|
|
|
|
The security attribute namespace is used by kernel security modules,
|
2015-04-22 07:27:03 +00:00
|
|
|
such as Security Enhanced Linux, and also to implement file capabilities (see
|
|
|
|
.BR capabilities (7)).
|
2015-04-22 06:28:34 +00:00
|
|
|
Read and write access permissions to security attributes depend on the
|
|
|
|
policy implemented for each security attribute by the security module.
|
|
|
|
When no security module is loaded, all processes have read access to
|
|
|
|
extended security attributes, and write access is limited to processes
|
2015-04-22 07:01:08 +00:00
|
|
|
that have the
|
|
|
|
.B CAP_SYS_ADMIN
|
|
|
|
capability.
|
2015-04-22 06:28:34 +00:00
|
|
|
.SS Extended system attributes
|
|
|
|
Extended system attributes are used by the kernel to store system
|
2015-04-22 07:27:03 +00:00
|
|
|
objects such as Access Control Lists.
|
2015-04-22 06:50:55 +00:00
|
|
|
Read and write
|
2015-04-22 06:28:34 +00:00
|
|
|
access permissions to system attributes depend on the policy implemented
|
|
|
|
for each system attribute implemented by filesystems in the kernel.
|
|
|
|
.SS Trusted extended attributes
|
|
|
|
Trusted extended attributes are visible and accessible only to processes that
|
2015-04-22 07:01:08 +00:00
|
|
|
have the
|
|
|
|
.B CAP_SYS_ADMIN
|
2015-04-22 07:33:49 +00:00
|
|
|
capability.
|
2015-04-22 06:28:34 +00:00
|
|
|
Attributes in this class are used to implement mechanisms in user
|
|
|
|
space (i.e., outside the kernel) which keep information in extended attributes
|
|
|
|
to which ordinary processes should not have access.
|
|
|
|
.SS Extended user attributes
|
|
|
|
Extended user attributes may be assigned to files and directories for
|
|
|
|
storing arbitrary additional information such as the mime type,
|
2015-04-22 06:50:55 +00:00
|
|
|
character set or encoding of a file.
|
|
|
|
The access permissions for user
|
2015-04-22 07:42:32 +00:00
|
|
|
attributes are defined by the file permission bits:
|
|
|
|
read permission is required to retrieve the attribute value,
|
|
|
|
and writer permission is required to change it.
|
2015-04-22 06:28:34 +00:00
|
|
|
.PP
|
|
|
|
The file permission bits of regular files and directories are
|
|
|
|
interpreted differently from the file permission bits of special files
|
2015-04-22 06:50:55 +00:00
|
|
|
and symbolic links.
|
|
|
|
For regular files and directories the file
|
2015-04-22 06:28:34 +00:00
|
|
|
permission bits define access to the file's contents, while for device special
|
|
|
|
files they define access to the device described by the special file.
|
2015-04-22 06:50:55 +00:00
|
|
|
The file permissions of symbolic links are not used in access checks.
|
|
|
|
These differences would allow users to consume filesystem resources in
|
|
|
|
a way not controllable by disk quotas for group or world writable
|
|
|
|
special files and directories.
|
2015-04-22 06:28:34 +00:00
|
|
|
.PP
|
2015-04-22 06:50:55 +00:00
|
|
|
For this reason,
|
2015-04-22 07:35:21 +00:00
|
|
|
extended user attributes are allowed only for regular files and directories,
|
2015-04-22 06:50:55 +00:00
|
|
|
and access to extended user attributes is restricted to the
|
2015-04-22 06:28:34 +00:00
|
|
|
owner and to users with appropriate capabilities for directories with the
|
|
|
|
sticky bit set (see the
|
|
|
|
.BR chmod (1)
|
2015-04-22 11:44:16 +00:00
|
|
|
manual page for an explanation of the sticky bit).
|
2015-04-22 06:54:38 +00:00
|
|
|
.SS Filesystem differences
|
2015-04-22 06:28:34 +00:00
|
|
|
The kernel and the filesystem may place limits on the maximum number
|
|
|
|
and size of extended attributes that can be associated with a file.
|
2015-04-22 08:06:30 +00:00
|
|
|
The VFS imposes limitations that an attribute names is limited to 255 bytes
|
2015-04-22 11:46:26 +00:00
|
|
|
and an attribute value is limited to 64 kB.
|
|
|
|
The list of attribute names that
|
2015-04-22 13:01:19 +00:00
|
|
|
can be returned is also limited to 64 kB
|
|
|
|
(see BUGS in
|
|
|
|
.BR listxattr (2)).
|
2015-04-22 08:06:30 +00:00
|
|
|
|
2015-04-22 08:03:37 +00:00
|
|
|
Some filesystems, such as Reiserfs (and, historically, ext2 and ext3),
|
|
|
|
require the filesystem to be mounted with the
|
2015-04-22 06:28:34 +00:00
|
|
|
.B user_xattr
|
|
|
|
mount option in order for extended user attributes to be used.
|
|
|
|
.PP
|
2015-04-22 08:12:43 +00:00
|
|
|
In the current ext2, ext3, and ext4 filesystem implementations,
|
2015-04-22 08:12:08 +00:00
|
|
|
the total bytes used by the names and values of all of a files
|
|
|
|
extended attributes must fit in a single filesystem block (1024, 2048
|
2015-04-22 06:28:34 +00:00
|
|
|
or 4096 bytes, depending on the block size specified when the
|
|
|
|
filesystem was created).
|
|
|
|
.PP
|
2015-04-22 07:17:52 +00:00
|
|
|
In the Btrfs, XFS, and Reiserfs filesystem implementations, there is no
|
2015-04-22 08:06:30 +00:00
|
|
|
practical limit on the number of extended attributes
|
2015-04-22 06:28:34 +00:00
|
|
|
associated with a file, and the algorithms used to store extended
|
|
|
|
attribute information on disk are scalable.
|
2015-04-22 08:31:35 +00:00
|
|
|
|
|
|
|
In the JFS, XFS, and Reiserfs filesystem implementations,
|
|
|
|
the limit on bytes used in an EA value is the ceiling imposed by the VFS.
|
2015-04-22 08:38:31 +00:00
|
|
|
|
|
|
|
In the Btrfs filesystem implementation,
|
|
|
|
the total bytes used for the name, value, and implementation overhead bytes
|
|
|
|
is limited to the filesystem
|
|
|
|
.I nodesize
|
2015-04-22 11:44:16 +00:00
|
|
|
value (16 kB by default).
|
2015-04-22 07:20:43 +00:00
|
|
|
.SH CONFORMING TO
|
|
|
|
Extended attributes are not specified in POSIX.1, but some other systems
|
|
|
|
(e.g., the BSDs and Solaris) provide a similar feature.
|
2015-04-22 07:39:40 +00:00
|
|
|
.SH NOTES
|
2015-04-22 06:28:34 +00:00
|
|
|
Since the filesystems on which extended attributes are stored might also
|
|
|
|
be used on architectures with a different byte order and machine word
|
2015-04-22 07:21:44 +00:00
|
|
|
size, care should be taken to store attribute values in an
|
|
|
|
architecture-independent format.
|
2015-04-22 12:35:54 +00:00
|
|
|
|
|
|
|
This page was formerly named
|
|
|
|
.BR attr (5).
|
2015-04-22 06:52:12 +00:00
|
|
|
.\" .SH AUTHORS
|
|
|
|
.\" Andreas Gruenbacher,
|
|
|
|
.\" .RI < a.gruenbacher@bestbits.at >
|
|
|
|
.\" and the SGI XFS development team,
|
|
|
|
.\" .RI < linux-xfs@oss.sgi.com >.
|
2015-04-22 06:28:34 +00:00
|
|
|
.SH SEE ALSO
|
2015-04-22 07:01:08 +00:00
|
|
|
.BR getfattr (1),
|
2015-04-22 07:11:27 +00:00
|
|
|
.BR setfattr (1),
|
|
|
|
.BR getxattr (2),
|
|
|
|
.BR listxattr (2),
|
|
|
|
.BR removexattr (2),
|
|
|
|
.BR setxattr (2),
|
|
|
|
.BR acl (5),
|
|
|
|
.BR capabilities (7)
|