Searched hist:"866 eef48" (Results 1 – 4 of 4) sorted by relevance
/openbmc/linux/include/uapi/linux/ |
H A D | gfs2_ondisk.h | 866eef48 Fri Feb 05 11:10:18 CST 2021 Andreas Gruenbacher <agruenba@redhat.com> gfs2: Add trusted xattr support
Add support for an additional filesystem version (sb_fs_format = 1802). When a filesystem with the new version is mounted, the filesystem supports "trusted.*" xattrs.
In addition, version 1802 filesystems implement a form of forward compatibility for xattrs: when xattrs with an unknown prefix (ea_type) are found on a version 1802 filesystem, those attributes are not shown by listxattr, and they are not accessible by getxattr, setxattr, or removexattr.
This mechanism might turn out to be what we need in the future, but if not, we can always bump the filesystem version and break compatibility instead.
Signed-off-by: Andreas Gruenbacher <agruenba@redhat.com> Signed-off-by: Andrew Price <anprice@redhat.com>
|
/openbmc/linux/fs/gfs2/ |
H A D | super.h | 866eef48 Fri Feb 05 11:10:18 CST 2021 Andreas Gruenbacher <agruenba@redhat.com> gfs2: Add trusted xattr support
Add support for an additional filesystem version (sb_fs_format = 1802). When a filesystem with the new version is mounted, the filesystem supports "trusted.*" xattrs.
In addition, version 1802 filesystems implement a form of forward compatibility for xattrs: when xattrs with an unknown prefix (ea_type) are found on a version 1802 filesystem, those attributes are not shown by listxattr, and they are not accessible by getxattr, setxattr, or removexattr.
This mechanism might turn out to be what we need in the future, but if not, we can always bump the filesystem version and break compatibility instead.
Signed-off-by: Andreas Gruenbacher <agruenba@redhat.com> Signed-off-by: Andrew Price <anprice@redhat.com>
|
H A D | xattr.c | 866eef48 Fri Feb 05 11:10:18 CST 2021 Andreas Gruenbacher <agruenba@redhat.com> gfs2: Add trusted xattr support
Add support for an additional filesystem version (sb_fs_format = 1802). When a filesystem with the new version is mounted, the filesystem supports "trusted.*" xattrs.
In addition, version 1802 filesystems implement a form of forward compatibility for xattrs: when xattrs with an unknown prefix (ea_type) are found on a version 1802 filesystem, those attributes are not shown by listxattr, and they are not accessible by getxattr, setxattr, or removexattr.
This mechanism might turn out to be what we need in the future, but if not, we can always bump the filesystem version and break compatibility instead.
Signed-off-by: Andreas Gruenbacher <agruenba@redhat.com> Signed-off-by: Andrew Price <anprice@redhat.com>
|
H A D | ops_fstype.c | 866eef48 Fri Feb 05 11:10:18 CST 2021 Andreas Gruenbacher <agruenba@redhat.com> gfs2: Add trusted xattr support
Add support for an additional filesystem version (sb_fs_format = 1802). When a filesystem with the new version is mounted, the filesystem supports "trusted.*" xattrs.
In addition, version 1802 filesystems implement a form of forward compatibility for xattrs: when xattrs with an unknown prefix (ea_type) are found on a version 1802 filesystem, those attributes are not shown by listxattr, and they are not accessible by getxattr, setxattr, or removexattr.
This mechanism might turn out to be what we need in the future, but if not, we can always bump the filesystem version and break compatibility instead.
Signed-off-by: Andreas Gruenbacher <agruenba@redhat.com> Signed-off-by: Andrew Price <anprice@redhat.com>
|