Hello,
For several requests, FUSE userspace returns a struct stat to the
kernel. struct stat includes an st_ino field, but FUSE generally has a
separate field for the inode (e.g. fuse_entry_param.ino vs
fuse_entry_param.attr.st_ino).
Does the kernel use the st_ino value at all, or is just passed through
to userspace?
If it is just passed through, is there a need for st_ino to match the
"real" inode?
Background:
Given that userspace has no use for inode values other than comparing
them for equality, I would have expected that st_ino can basically be
anything as long as there's some 1:1 mapping to kernel inodes. However,
I have seen changes in userspace behavior when setting st_ino to the
kernel inode (previously it was set to some other value by accident).
Thanks!
-Nikolaus
--
GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
