From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Nikita Danilov <Nikita@Namesys.COM>
Cc: Neil Brown <neilb@cse.unsw.edu.au>,
Hans-Peter Jansen <hpj@urpla.net>,
linux-kernel@vger.kernel.org,
Reiserfs mail-list <Reiserfs-List@Namesys.COM>
Subject: Re: [BUG] symlink problem with knfsd and reiserfs
Date: Tue, 15 Jan 2002 14:40:29 +0100 [thread overview]
Message-ID: <15428.12621.682479.589568@charged.uio.no> (raw)
In-Reply-To: <15428.14268.730698.637522@laputa.namesys.com>
In-Reply-To: <20020115115019.89B55143B@shrek.lisa.de> <15428.6953.453942.415989@charged.uio.no> <15428.14268.730698.637522@laputa.namesys.com>
>>>>> " " == Nikita Danilov <Nikita@Namesys.COM> writes:
> Yes, inode->i_generation is stored in the file handle:
> fs/reiserfs/inode.c:reiserfs_dentry_to_fh().
But what is stored in inode->i_generation? AFAICS
inode->i_generation = le32_to_cpu (INODE_PKEY (inode)->k_dir_id);
which appears not to be a unique generation count. Isn't that instead
the directory's object id?
The point of i_generation is to provide a unique number that changes
every time you reuse the inode number.
Cheers,
Trond
next prev parent reply other threads:[~2002-01-15 13:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-15 14:07 Nikita Danilov
2002-01-15 11:50 ` Hans-Peter Jansen
2002-01-15 12:06 ` Trond Myklebust
2002-01-15 13:40 ` Trond Myklebust [this message]
2002-01-15 13:40 ` David L. Parsley
2002-01-15 15:27 ` Nikita Danilov
2002-01-15 15:38 ` Trond Myklebust
2002-01-15 16:47 ` Nikita Danilov
2002-01-15 16:31 ` Hans-Peter Jansen
2002-01-15 17:53 ` Nikita Danilov
2002-01-15 18:01 ` David L. Parsley
2002-01-15 18:14 ` Hans-Peter Jansen
2002-01-15 19:25 ` Nikita Danilov
2002-01-15 19:30 ` Nikita Danilov
2002-01-15 15:32 ` Hans-Peter Jansen
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=15428.12621.682479.589568@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=Nikita@Namesys.COM \
--cc=Reiserfs-List@Namesys.COM \
--cc=hpj@urpla.net \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®