[Bug 2006483] Re: Fails autopkgtests when tested against fuse3 >= 3.13

[Graham Inggs]

This is a regression in fuse3 3.13.0, see upstream issue:

https://github.com/libfuse/libfuse/issues/730

Confirmed by modifying the failing command in ostree's tests/test-
rofiles-fuse.sh from:

setfattr -n user.foo -v bar mnt/anewfile-for-fuse

to:

setfattr -n 12345678user.foo -v bar mnt/anewfile-for-fuse


** Bug watch added: github.com/libfuse/libfuse/issues #730
   https://github.com/libfuse/libfuse/issues/730

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to fuse3 in Ubuntu.
https://bugs.launchpad.net/bugs/2006483

Title:
  Fails autopkgtests when tested against fuse3 >= 3.13

Status in fuse3 package in Ubuntu:
  New
Status in ostree package in Ubuntu:
  New

Bug description:
  The autopkgtest in `tests/test-rofiles-fuse.sh` (executed via `gnome-
  desktop-testing-runner libostree/test-rofiles-fuse.sh.test`) fails to
  execute `setfattr -n user.foo -v bar mnt/anewfile-for-fuse` with the
  error message "setfattr: mnt/anewfile-for-fuse: Numerical result out
  of range".

  It's unclear if this is related to glibc, FUSE_USE_VERSION, kernel
  fuse protocol or another component.

  On Debian this specific test is skipped, due to missing the "capsh" binary (libcap2-bin) in the test env:
  ```
  /usr/libexec/installed-tests/libostree/libtest.sh: line 688: capsh: command not found
  1..0 # SKIP No cap_sys_admin in bounding set, can't use FUSE
  ```

  The relevant log (inside an Ubuntu autopkgtest qemu runner) is
  provided here:

  ```
  $ ../tests/test-rofiles-fuse.sh
  Copying gpghome to /tmp/autopkgtest.Eaudsf/build.b3k/src/tmp4
  checking for xattrs.../usr/bin/setfattr
  /tmp/autopkgtest.Eaudsf/build.b3k/src/tmp4 /tmp/autopkgtest.Eaudsf/build.b3k/src/tmp4
  # testlabel.txt: security.selinux: No such attribute
  Unable to retrieve SELinux label, assuming disabled
  /tmp/autopkgtest.Eaudsf/build.b3k/src/tmp4
  done
  checking for overlayfs whiteouts...done
  /usr/bin/setfattr
  d9793c4639f817fb95e3f1ae7a3f0571826db12a28baffaa3b3510f2ef0434a4
  812152c68bb9c0b2a3bfcafeb5c4a4aa53827d8df5eeb755fe307f6a68f0febf
  fsck objects (20/20) [=============] 100%
  object fsck of 2 commits completed successfully - no errors found.
  1..12
  a122802794e487785d14b58fe8969ab8716fd5c4c0ceed7de5c76061cd93f896
  ok mount
  ok failed inplace mutation (open O_TRUNCATE)
  ok failed mutation chmod + chown
  setfattr: mnt/firstfile-link: Read-only file system
  ok new content
  setfattr: mnt/anewfile-for-fuse: Numerical result out of range
  Unexpected nonzero exit status 1 while running: setfattr -n user.foo -v bar mnt/anewfile-for-fuse
  gpg-connect-agent: no running gpg-agent - starting '/usr/bin/gpg-agent'
  gpg-connect-agent: waiting for the agent to come up ... (5s)
  gpg-connect-agent: connection to agent established
  OK closing connection
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fuse3/+bug/2006483/+subscriptions