From: Nikolaus Rath <Nikolaus@rath.org>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: "Jean-Pierre André" <jean-pierre.andre@wanadoo.fr>,
fuse-devel <fuse-devel@lists.sourceforge.net>,
linux-fsdevel@vger.kernel.org
Subject: Re: [fuse-devel] [fuse] Relevance of st_ino values
Date: Mon, 11 Feb 2019 20:44:03 +0000 [thread overview]
Message-ID: <878symukbw.fsf@vostro.rath.org> (raw)
In-Reply-To: <CAJfpegsbKjB6_PtvNNtSq0W8R3E+M8wZ6JAcvVhvE3fZk5FyAw@mail.gmail.com> (Miklos Szeredi's message of "Mon, 11 Feb 2019 16:59:18 +0100")
On Feb 11 2019, Miklos Szeredi <miklos@szeredi.hu> wrote:
> On Mon, Feb 11, 2019 at 12:18 PM Jean-Pierre André
> <jean-pierre.andre@wanadoo.fr> 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.«
next prev parent reply other threads:[~2019-02-11 20:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-10 21:15 [fuse] Relevance of st_ino values Nikolaus Rath
2019-02-11 11:18 ` Jean-Pierre André
2019-02-11 15:59 ` [fuse-devel] " Miklos Szeredi
2019-02-11 20:44 ` Nikolaus Rath [this message]
2019-02-12 9:02 ` Miklos Szeredi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878symukbw.fsf@vostro.rath.org \
--to=nikolaus@rath.org \
--cc=fuse-devel@lists.sourceforge.net \
--cc=jean-pierre.andre@wanadoo.fr \
--cc=linux-fsdevel@vger.kernel.org \
--cc=miklos@szeredi.hu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).