From: Jeremy Allison <jra@samba.org>
To: Amir Goldstein <amir73il@gmail.com>
Cc: "Darrick J. Wong" <djwong@kernel.org>,
Christoph Hellwig <hch@infradead.org>,
Trond Myklebust <trond.myklebust@hammerspace.com>,
Dan Carpenter <dan.carpenter@oracle.com>,
richard.sharpe@primarydata.com,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
lance.shelton@hammerspace.com,
Anna Schumaker <Anna.Schumaker@netapp.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Linux API <linux-api@vger.kernel.org>,
CIFS <linux-cifs@vger.kernel.org>,
ntfs3@lists.linux.dev, Steve French <sfrench@samba.org>,
Konstantin Komarov <almaz.alexandrovich@paragon-software.com>,
Ralph Boehme <slow@samba.org>
Subject: Re: [bug report] NFS: Support statx_get and statx_set ioctls
Date: Wed, 12 Jan 2022 22:30:57 -0800 [thread overview]
Message-ID: <Yd/HIYsCBPH5jPmS@jeremy-acer> (raw)
In-Reply-To: <CAOQ4uxh7wpxx2H6Vpm26OdigXbWCCLO1xbFapupvLCn8xOiL=w@mail.gmail.com>
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.
Samba uses btime for "birth time", and will use statx
to get it from the filesystem but then store it in
the dos.attribute EA so it can be modified if the
client sets it.
next prev parent reply other threads:[~2022-01-13 6:55 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 [this message]
2022-01-13 14:58 ` Trond Myklebust
2022-01-13 17:50 ` Jeremy Allison
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=Yd/HIYsCBPH5jPmS@jeremy-acer \
--to=jra@samba.org \
--cc=Anna.Schumaker@netapp.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=lance.shelton@hammerspace.com \
--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=richard.sharpe@primarydata.com \
--cc=sfrench@samba.org \
--cc=slow@samba.org \
--cc=trond.myklebust@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).