Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
lgetxattr can't read the attribute of a softlink file with ntfs FS, shows "lgetxattr: No data available". on one hand, it's lgetxattr issue, on other hand, may lsetxattr doesn't work to softlink
Version-Release number of selected component (if applicable):
libguestfs-1.22.2-1.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
# guestfish -N fs:ntfs
Welcome to guestfish, the guest filesystem shell for
editing virtual machine filesystems and disk images.
Type: 'help' for help on commands
'man' to read the manual
'quit' to quit the shell
><fs> trace 1
><fs> mount-options user_xattr /dev/sda1 /
libguestfs: trace: mount_options "user_xattr" "/dev/sda1" "/"
libguestfs: trace: mount_options = 0
><fs> touch /test.txt
libguestfs: trace: touch "/test.txt"
libguestfs: trace: touch = 0
><fs> ln-s /test.txt /link.txt
libguestfs: trace: ln_s "/test.txt" "/link.txt"
libguestfs: trace: ln_s = 0
><fs> ll /
libguestfs: trace: ll "/"
libguestfs: trace: ll = "total 9\ndrwxrwxrwx 1 root root 4096 Jun 8 10:58 .\ndrwxr-xr-x 23 root root 4096 Jun 8 10:57 ..\nlrwxrwxrwx 1 root root 26 Jun 8 10:58 link.txt -> /test.txt\n-rwxrwxrwx 1 root root 0 Jun 8 10:57 test.txt\n"
total 9
drwxrwxrwx 1 root root 4096 Jun 8 10:58 .
drwxr-xr-x 23 root root 4096 Jun 8 10:57 ..
lrwxrwxrwx 1 root root 26 Jun 8 10:58 link.txt -> /test.txt
-rwxrwxrwx 1 root root 0 Jun 8 10:57 test.txt
><fs> lsetxattr security.name "hello" 5 /link.txt
libguestfs: trace: lsetxattr "security.name" "hello" 5 "/link.txt"
libguestfs: trace: lsetxattr = 0
><fs> lsetxattr security.type "ascii file" 10 /link.txt
libguestfs: trace: lsetxattr "security.type" "ascii file" 10 "/link.txt"
libguestfs: trace: lsetxattr = 0
><fs> lgetxattr /link.txt security.name
libguestfs: trace: lgetxattr "/link.txt" "security.name"
libguestfs: trace: lgetxattr = NULL (error)
libguestfs: error: lgetxattr: lgetxattr: No data available
><fs>
Actual results:
lgetxattr read a specified attribute failed
Expected results:
lgetxattrs can work well
Additional info:
1. It works well with ext FS
2. regression, works with libguestfs-1.20.2-1.el7.x86_64
Comment 2Richard W.M. Jones
2013-06-10 15:27:30 UTC
I'm fairly dubious that:
><fs> lsetxattr security.name "hello" 5 /link.txt
should work at all. Note *l*setxattr should set the attribute
on the symbolic link, not on the target file. But does it make
sense to set security.* attributes on the symbolic link? I
guess the answer depends on details of ntfs-3g or even of the
NTFS file format itself.
Comment 3Richard W.M. Jones
2013-07-18 22:19:41 UTC
Using user.* attributes instead of security.* attributes
(see https://bugzilla.redhat.com/show_bug.cgi?id=972292#c2)
I get the following error:
$ guestfish -N fs:ntfs -m /dev/sda1:/:user_xattr touch /test.txt : ln-s /test.txt /link.txt : lsetxattr user.name "hello" 5 /link.txt : lsetxattr user.type "ascii file" 10 /link.txt : lgetxattr /link.txt user.name : echo : lgetxattrs /link.txt
libguestfs: error: lsetxattr: setxattr: Operation not permitted
So it seems that ntfs-3g is not happy with us setting xattrs
on symbolic links (although this is possible for ordinary
Unix-like filesystems).
Things work through the symlink if you use setxattr/getxattr
instead:
$ guestfish -N fs:ntfs -m /dev/sda1:/:user_xattr touch /test.txt : ln-s /test.txt /link.txt : setxattr user.name "hello" 5 /link.txt : setxattr user.type "ascii file" 10 /link.txt : getxattr /link.txt user.name : echo : getxattrs /link.txt
hello
[0] = {
attrname: user.name
attrval: hello
}
[1] = {
attrname: user.type
attrval: ascii file
}
I'm not sure what to conclude about this, except that NTFS
is a strange not-Unix-like filesystem, and ntfs-3g works
through FUSE so everything's complicated.
Probably not something we need to worry about.
Comment 5Richard W.M. Jones
2014-04-25 09:22:58 UTC
I don't think this is something we care about. As I said
in comment 3, ntfs is a non-Unix filesystem, and ntfs-3g works
via FUSE which complicates things. In addition ntfs has its
own way of doing symbolic links (using a strange binary format).
Description of problem: lgetxattr can't read the attribute of a softlink file with ntfs FS, shows "lgetxattr: No data available". on one hand, it's lgetxattr issue, on other hand, may lsetxattr doesn't work to softlink Version-Release number of selected component (if applicable): libguestfs-1.22.2-1.el7.x86_64 How reproducible: 100% Steps to Reproduce: # guestfish -N fs:ntfs Welcome to guestfish, the guest filesystem shell for editing virtual machine filesystems and disk images. Type: 'help' for help on commands 'man' to read the manual 'quit' to quit the shell ><fs> trace 1 ><fs> mount-options user_xattr /dev/sda1 / libguestfs: trace: mount_options "user_xattr" "/dev/sda1" "/" libguestfs: trace: mount_options = 0 ><fs> touch /test.txt libguestfs: trace: touch "/test.txt" libguestfs: trace: touch = 0 ><fs> ln-s /test.txt /link.txt libguestfs: trace: ln_s "/test.txt" "/link.txt" libguestfs: trace: ln_s = 0 ><fs> ll / libguestfs: trace: ll "/" libguestfs: trace: ll = "total 9\ndrwxrwxrwx 1 root root 4096 Jun 8 10:58 .\ndrwxr-xr-x 23 root root 4096 Jun 8 10:57 ..\nlrwxrwxrwx 1 root root 26 Jun 8 10:58 link.txt -> /test.txt\n-rwxrwxrwx 1 root root 0 Jun 8 10:57 test.txt\n" total 9 drwxrwxrwx 1 root root 4096 Jun 8 10:58 . drwxr-xr-x 23 root root 4096 Jun 8 10:57 .. lrwxrwxrwx 1 root root 26 Jun 8 10:58 link.txt -> /test.txt -rwxrwxrwx 1 root root 0 Jun 8 10:57 test.txt ><fs> lsetxattr security.name "hello" 5 /link.txt libguestfs: trace: lsetxattr "security.name" "hello" 5 "/link.txt" libguestfs: trace: lsetxattr = 0 ><fs> lsetxattr security.type "ascii file" 10 /link.txt libguestfs: trace: lsetxattr "security.type" "ascii file" 10 "/link.txt" libguestfs: trace: lsetxattr = 0 ><fs> lgetxattr /link.txt security.name libguestfs: trace: lgetxattr "/link.txt" "security.name" libguestfs: trace: lgetxattr = NULL (error) libguestfs: error: lgetxattr: lgetxattr: No data available ><fs> Actual results: lgetxattr read a specified attribute failed Expected results: lgetxattrs can work well Additional info: 1. It works well with ext FS 2. regression, works with libguestfs-1.20.2-1.el7.x86_64