From: Anton Altaparmakov <aia21@cam.ac.uk>
To: Christoph Hellwig <hch@infradead.org>
Cc: nfs@lists.sourceforge.net, linux-fsdevel@vger.kernel.org
Subject: Re: i_generation = 0 special casing
Date: Wed, 24 Nov 2004 12:25:04 +0000 [thread overview]
Message-ID: <1101299105.15596.22.camel@imp.csi.cam.ac.uk> (raw)
In-Reply-To: <20041124094320.GA10206@infradead.org>
On Wed, 2004-11-24 at 09:43 +0000, Christoph Hellwig wrote:
> export_iget (and routines based on it such as xfs_vget) check for
> i_generation beeing 0 meaning that every generation is okay. Where in
> the NFS code is this wildcard needed?
I didn't have anything to do with the i_generation handling in NFS but
at least NTFS takes i_generation beeing 0 meaning that every generation
is ok. (That is how Windows NTFS does it so we do the same. It allows
to disable generation checking by setting all i_generations to 0 on a
volume.)
> I had to find out that XFS starts it's i_generation at zero and either
> I have to fix up the i_generation or drop this wildcard if it's not
> actually used.
In NTFS I start i_generation at 1 and when it reaches 0xffff I wrap it
to 1 again, skipping zero. (On disk it is 16 bits on NTFS.)
Best regards,
Anton
--
Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @)
Unix Support, Computing Service, University of Cambridge, CB2 3QH, UK
Linux NTFS maintainer / IRC: #ntfs on irc.freenode.net
WWW: http://linux-ntfs.sf.net/ & http://www-stu.christs.cam.ac.uk/~aia21/
next prev parent reply other threads:[~2004-11-24 12:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-24 9:43 i_generation = 0 special casing Christoph Hellwig
2004-11-24 12:25 ` Anton Altaparmakov [this message]
2004-11-24 22:48 ` Neil Brown
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=1101299105.15596.22.camel@imp.csi.cam.ac.uk \
--to=aia21@cam.ac.uk \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=nfs@lists.sourceforge.net \
/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).