From: Eric Sandeen <sandeen@redhat.com>
To: Christoph Hellwig <hch@infradead.org>,
Jeff Layton <jlayton@redhat.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
esandeen@redhat.com, aviro@redhat.com
Subject: Re: [PATCH 2/3] change libfs sb creation routines to avoid collisions with their root inodes
Date: Wed, 10 Jan 2007 15:51:33 -0600 [thread overview]
Message-ID: <45A55FE5.80907@redhat.com> (raw)
In-Reply-To: <20070110212215.GB4425@infradead.org>
Christoph Hellwig wrote:
>
>> return -ENOMEM;
>> + /* set to high value to try and avoid collisions with loop below */
>> + inode->i_ino = 0xffffffff;
>> + insert_inode_hash(inode);
>
> This is odd. Can't we just add some constant base to the loop below?
>
I thought the same thing, but Jeff pointed out that
nfsctl_transaction_write does ops based on inode numbers, and they maybe
can't move around?
rv = write_op[ino](file, data, size);
However, nfsd's call to simple_fill_super already sends in a set of
files starting at inode 2:
enum {
NFSD_Root = 1,
NFSD_Svc,
...
static struct tree_descr nfsd_files[] = {
[NFSD_Svc] = {".svc", &transaction_ops, S_IWUSR},
...
return simple_fill_super(sb, 0x6e667364, nfsd_files);
which does...
for (i = 0; !files->name || files->name[0]; i++, files++) {
if (!files->name)
continue;
...
inode->i_ino = i;
So I think it's already expecting the root inode at one, and the other
files starting at 2?
-Eric
next prev parent reply other threads:[~2007-01-10 21:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-08 20:47 [PATCH 2/3] change libfs sb creation routines to avoid collisions with their root inodes Jeff Layton
2007-01-10 21:22 ` Christoph Hellwig
2007-01-10 21:51 ` Eric Sandeen [this message]
2007-01-11 16:46 ` Jeff Layton
-- strict thread matches above, loose matches on Subject: below --
2007-01-16 18:57 Jeff Layton
2007-01-11 20:15 Jeff Layton
2007-01-11 20:08 Jeff Layton
2007-01-11 19:43 Jeff Layton
2006-12-29 19:11 Jeff Layton
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=45A55FE5.80907@redhat.com \
--to=sandeen@redhat.com \
--cc=aviro@redhat.com \
--cc=esandeen@redhat.com \
--cc=hch@infradead.org \
--cc=jlayton@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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).