From: Jeremy Allison <jra@samba.org>
To: Trond Myklebust <trondmy@hammerspace.com>
Cc: "amir73il@gmail.com" <amir73il@gmail.com>,
Lance Shelton <Lance.Shelton@hammerspace.com>,
Richard Sharpe <Richard.Sharpe@hammerspace.com>,
"linux-cifs@vger.kernel.org" <linux-cifs@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-api@vger.kernel.org" <linux-api@vger.kernel.org>,
"ntfs3@lists.linux.dev" <ntfs3@lists.linux.dev>,
"hch@infradead.org" <hch@infradead.org>,
"almaz.alexandrovich@paragon-software.com"
<almaz.alexandrovich@paragon-software.com>,
"djwong@kernel.org" <djwong@kernel.org>,
"dan.carpenter@oracle.com" <dan.carpenter@oracle.com>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"Anna.Schumaker@netapp.com" <Anna.Schumaker@netapp.com>,
"slow@samba.org" <slow@samba.org>,
"sfrench@samba.org" <sfrench@samba.org>
Subject: Re: [bug report] NFS: Support statx_get and statx_set ioctls
Date: Thu, 13 Jan 2022 09:50:44 -0800 [thread overview]
Message-ID: <YeBmdHzvSlIIwmIM@jeremy-acer> (raw)
In-Reply-To: <3cf76cc19f12f3e9da2eae7fe12e2719c8e499f8.camel@hammerspace.com>
On Thu, Jan 13, 2022 at 02:58:19PM +0000, Trond Myklebust wrote:
>On Wed, 2022-01-12 at 22:30 -0800, Jeremy Allison wrote:
>> On Thu, Jan 13, 2022 at 05:52:40AM +0200, Amir Goldstein wrote:
>> >
>> > To add one more terminology to the mix - when Samba needed to cope
>> > with these two terminologies they came up with itime for
>> > "instantiation time"
>> > (one may also consider it "immutable time").
>>
>> No, that's not what itime is. It's used as the basis
>> for the fileid return as MacOSX clients insist on no-reuse
>> of inode numbers when a file is deleted then re-created,
>> and ext4 will re-use the same inode.
>
>So basically it serves more or less the same purpose as the generation
>counter that most Linux filesystems use in the filehandle to provide
>similar only-once semantics?
Kind of, although we moved it recently to be
a current_time + random skew as the timestamp
resolution in ext4 just wasn't enough to get us
unique fileids.
next prev parent reply other threads:[~2022-01-13 17:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220111074309.GA12918@kili>
[not found] ` <Yd1ETmx/HCigOrzl@infradead.org>
2022-01-12 7:57 ` [bug report] NFS: Support statx_get and statx_set ioctls Amir Goldstein
2022-01-12 17:43 ` Darrick J. Wong
2022-01-13 3:52 ` Amir Goldstein
2022-01-13 6:30 ` Jeremy Allison
2022-01-13 14:58 ` Trond Myklebust
2022-01-13 17:50 ` Jeremy Allison [this message]
2022-01-13 15:01 ` Trond Myklebust
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=YeBmdHzvSlIIwmIM@jeremy-acer \
--to=jra@samba.org \
--cc=Anna.Schumaker@netapp.com \
--cc=Lance.Shelton@hammerspace.com \
--cc=Richard.Sharpe@hammerspace.com \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=amir73il@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=djwong@kernel.org \
--cc=hch@infradead.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=ntfs3@lists.linux.dev \
--cc=sfrench@samba.org \
--cc=slow@samba.org \
--cc=trondmy@hammerspace.com \
/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).