From: David Chow <davidchow@shaolinmicro.com>
To: linux-fsdevel@vger.kernel.org, neilb@cse.unsw.edu.au
Subject: i_generation consistency
Date: Tue, 26 Nov 2002 18:11:21 +0800 [thread overview]
Message-ID: <3DE348C9.4000404@shaolinmicro.com> (raw)
Hi Neil,
I am writing a file system and having problem implementing the
i_generation of the inode. Should the i_generation be persistent in the
disk? Or it has to be changed every time the dcache shrinks or reload
after read_inode()? Should I check the i_generation in the fh_dentry()
ops and include it in file handle or leave it to the NFS clients and
nfsd and I should forget about implementing i_generation in file
handles. Can you please clarify? Thanks.
regards,
David Chow
next reply other threads:[~2002-11-26 10:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-26 10:11 David Chow [this message]
2002-11-26 12:58 ` i_generation consistency Neil Brown
2002-11-28 6:28 ` David Chow
[not found] ` <3DE5B746.1040300@shaolinmicro.com>
2002-12-01 23:00 ` 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=3DE348C9.4000404@shaolinmicro.com \
--to=davidchow@shaolinmicro.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/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).