From: Randy Dunlap <randy.dunlap@oracle.com>
To: Jeff Layton <jlayton@redhat.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] ensure i_ino uniqueness in filesystems without permanent inode numbers (via idr)
Date: Fri, 1 Dec 2006 08:52:27 -0800 [thread overview]
Message-ID: <20061201085227.2463b185.randy.dunlap@oracle.com> (raw)
In-Reply-To: <457040C4.1000002@redhat.com>
On Fri, 01 Dec 2006 09:48:36 -0500 Jeff Layton wrote:
> This patch is a proof of concept. It works, but still needs a bit of
> polish before it's ready for submission. First, the problems:
>
>
> This patch is a first step at correcting these problems. This adds 2 new
> functions, an idr_register and idr_unregister. Filesystems can call
> idr_register at inode creation time, and then at deletion time, we'll
> automatically unregister them.
s/idr_/iunique_/
> This patch also adds a new s_generation counter to the superblock.
> Because i_ino's can be reused so quickly, we don't want NFS getting
> confused when it happens. When iunique_register is called, we'll assign
> the s_generation value to the i_generation, and then increment it to
> help ensure that we get different filehandles.
>
> There are some things that need to be cleaned up, of course:
>
> - error handling for the idr calls
>
> - recheck all the possible places where the inode should be unhashed
>
> - don't attempt to remove inodes with values <100
Please explain that one. (May be obvious to some, but not to me.)
> - convert other filesystems
>
> - remove the static counter from new_inode and (maybe) eliminate iunique
>
> Comments and suggestions appreciated.
Better to post patches inline (for review) rather than as attachments.
Some (mostly style) comments on the patch:
+ rv = idr_pre_get(&inode->i_sb->s_inode_ids, GFP_KERNEL);
+ if (! rv)
+ return -ENOMEM;
if (!rv)
+ rv = idr_get_new_above(&inode->i_sb->s_inode_ids, inode,
+ max_reserved+1, (int *) &inode->i_ino);
max_reserved + 1,
+}
+
+EXPORT_SYMBOL(iunique_register);
No need for the extra blank line after the function closing
brace. Just put the EXPORT_SYMBOL immediately on the next line.
(in multiple places)
@@ -1681,6 +1688,8 @@ extern void inode_init_once(struct inode
extern void iput(struct inode *);
extern struct inode * igrab(struct inode *);
extern ino_t iunique(struct super_block *, ino_t);
+extern int iunique_register(struct inode *, int);
+extern void iunique_unregister(struct inode *);
extern int inode_needs_sync(struct inode *inode);
extern void generic_delete_inode(struct inode *inode);
extern void generic_drop_inode(struct inode *inode);
Some of these have a parameter name, some don't.
Having a (meaningful) parameter name is strongly preferred.
---
~Randy
next prev parent reply other threads:[~2006-12-01 16:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-01 14:48 [RFC][PATCH] ensure i_ino uniqueness in filesystems without permanent inode numbers (via idr) Jeff Layton
2006-12-01 16:52 ` Randy Dunlap [this message]
2006-12-01 17:21 ` Jeff Layton
2006-12-01 17:42 ` Randy Dunlap
2006-12-02 5:30 ` Brad Boyer
2006-12-03 2:56 ` Jeff Layton
2006-12-02 12:58 ` Brad Boyer
2006-12-03 11:52 ` Al Boldi
2006-12-03 12:49 ` Jeff Layton
-- strict thread matches above, loose matches on Subject: below --
2006-11-14 20:22 Jeff Layton
2006-11-14 20:26 ` Al Viro
2006-11-15 16:42 ` Jeff Layton
2006-11-15 16:44 ` Jeff Layton
2006-11-16 14:06 ` Al Viro
2006-11-16 14:34 ` Jeff Layton
2006-11-15 17:27 ` Matthew Wilcox
2006-11-15 17:56 ` Jörn Engel
2006-11-15 20:36 ` 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=20061201085227.2463b185.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--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).