Useless permission denied errors

[xeruf]

When I execute adbfs, I get this in stdout:

--*-- exec_command: adb shell "ls"
ls: ./verity_key: Permission denied
ls: ./ueventd.rc: Permission denied
ls: ./ueventd.qcom.rc: Permission denied
ls: ./service_contexts: Permission denied
ls: ./sepolicy: Permission denied
ls: ./selinux_version: Permission denied
ls: ./seapp_contexts: Permission denied
ls: ./init.zygote32.rc: Permission denied
ls: ./init.usb.rc: Permission denied
ls: ./init.usb.configfs.rc: Permission denied
ls: ./init.target.rc: Permission denied
ls: ./init.rc: Permission denied
ls: ./init.qcom.usb.sh: Permission denied
ls: ./init.qcom.usb.rc: Permission denied
ls: ./init.qcom.syspart_fixup.sh: Permission denied
ls: ./init.qcom.sh: Permission denied
ls: ./init.qcom.sensors.sh: Permission denied
ls: ./init.qcom.rc: Permission denied
ls: ./init.qcom.factory.rc: Permission denied
ls: ./init.qcom.early_boot.sh: Permission denied
ls: ./init.qcom.class_core.sh: Permission denied
ls: ./init.msm.usb.configfs.rc: Permission denied
ls: ./init.mdm.sh: Permission denied
ls: ./init.lenovo.target.rc: Permission denied
ls: ./init.lenovo.rc: Permission denied
ls: ./init.lenovo.log.rc: Permission denied
ls: ./init.lenovo.factory.rc: Permission denied
ls: ./init.lenovo.crash.rc: Permission denied
ls: ./init.lenovo.common.rc: Permission denied
ls: ./init.environ.rc: Permission denied
ls: ./init.class_main.sh: Permission denied
ls: ./init: Permission denied
ls: ./fstab.qcom: Permission denied
ls: ./file_contexts.bin: Permission denied
ls: ./default.prop: Permission denied

but since these are system-level files that nobody needs to access, they should simply be ignored instead of showing errors.

[spion]

Are you executing with -f - if so, thats debug output.

[xeruf]

Nope I am not, when executing with -f it outputs much more.

[codexp]

I confirm this. No -f flag used:

--*-- exec_command: adb shell "ls"
ls: ./modem_log: Permission denied
ls: ./mnvm2:0: Permission denied
ls: ./modem_fw: Permission denied
ls: ./sec_storage: Permission denied
ls: ./version.prop: Permission denied
ls: ./verity_key: Permission denied
ls: ./ueventd.rc: Permission denied
ls: ./rootscan.conf: Permission denied
ls: ./resetFactory.cfg: Permission denied
ls: ./init.zygote64_32.rc: Permission denied
ls: ./init.zygote32.rc: Permission denied
ls: ./init.usb.rc: Permission denied
ls: ./init.usb.configfs.rc: Permission denied
ls: ./init.rc: Permission denied
ls: ./init.environ.rc: Permission denied
ls: ./init: Permission denied
ls: ./fstab.zram768m: Permission denied
ls: ./fstab.zram512m: Permission denied
ls: ./fstab.zram256m: Permission denied
ls: ./fstab.zram2240m: Permission denied
ls: ./fstab.zram1536m: Permission denied
ls: ./fstab.zram1280m: Permission denied
ls: ./fstab.zram1024m: Permission denied

mount is successful btw.

[rien333]

Still the same, not a huge fan of the messages, bc I'm always worried they indicate something is wrong (they don't). Are they the result of adbfs first calling adb shell ls? And then why does it do that?

[O330oei]

add

[spion]

@rien333 I believe its requested by the OS when the volume is mounted (although not sure which component requests it, likely some of the gnome ones trying to get an early list of the root directory). I don't think its the first ls - we could remove that I suppose