Re: [fuse-devel] [fuse] Relevance of st_ino values

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Feb 11 2019, Miklos Szeredi <miklos@xxxxxxxxxx> wrote:
> On Mon, Feb 11, 2019 at 12:18 PM Jean-Pierre André
> <jean-pierre.andre@xxxxxxxxxx> wrote:
>>
>> Nikolaus Rath wrote:
>> > 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?
>
> st_ino value is not used in any way by the kernel, just passed through
> to userspace.

Thanks! And there is nothing that userspace can do with those numbers
other than comparing them to determine if two files are hardlinks of
each other, right? They cannot be passed back to the kernel in a
syscall?


Best,
-Nikolaus
-- 
GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

             »Time flies like an arrow, fruit flies like a Banana.«




[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]

  Powered by Linux