From: Andrew Morton <akpm@digeo.com>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PATCH - Don't remove inode from hash until filesystem has deleted it.
Date: Fri, 9 May 2003 15:24:10 -0700 [thread overview]
Message-ID: <20030509152410.39ede4b0.akpm@digeo.com> (raw)
In-Reply-To: <16057.46720.778667.845306@notabene.cse.unsw.edu.au>
Neil Brown <neilb@cse.unsw.edu.au> wrote:
>
>
> There is a small race with knfsd using iget to get an inode
> that is currently being deleted. This is because it is removed
> from the hash table *before* the filesystem gets to delete it.
> If nfsd does an iget in this window it will cause a read_inode which
> will return an apparently valid inode. However that inode will
> shortly be deleted from disc without knfsd noticing... until
> it is too late.
Cannot nfsd use igrab()?
> With this patch, the inode being deleted is left on the hash table,
> and if a lookup find an inode being freed in the hashtable, it waits
> in the inode waitqueue for the inode to be fully deleted.
Few things:
- Why the tests for I_CLEAR as well?
- There are lots of paths which set I_FREEING, and lots of paths which
unhash inodes. But only one path in which a waiter on
__wait_on_freeing_inode() gets woken up.
Are you sure there is sufficient coverage here? That there are no
paths by which someone goes to sleep on a freeing inode but never gets
woken up?
- wart: when a task gets woken in __wait_on_freeing_inode(), it doesn't
know that it got woken on behalf of the correct inode (hash collision).
So the inode can still be in state I_FREEING when
__wait_on_freeing_inode() returns.
Yeah, it happens that this is OK because the caller will just repeat the
search, but that sort of subtlety needs to be covered in commentary.
- Cleanups:
25-akpm/fs/inode.c | 10 ++++------
1 files changed, 4 insertions(+), 6 deletions(-)
diff -puN fs/inode.c~inode-unhashing-fix-cleanups fs/inode.c
--- 25/fs/inode.c~inode-unhashing-fix-cleanups Fri May 9 15:19:22 2003
+++ 25-akpm/fs/inode.c Fri May 9 15:20:20 2003
@@ -478,6 +478,7 @@ static struct inode * find_inode(struct
struct hlist_node *node;
struct inode * inode = NULL;
+repeat:
hlist_for_each (node, head) {
prefetch(node->next);
inode = hlist_entry(node, struct inode, i_hash);
@@ -487,8 +488,7 @@ static struct inode * find_inode(struct
continue;
if (inode->i_state & (I_FREEING|I_CLEAR)) {
__wait_on_freeing_inode(inode);
- node = head->first;
- continue;
+ goto repeat;
}
break;
}
@@ -504,6 +504,7 @@ static struct inode * find_inode_fast(st
struct hlist_node *node;
struct inode * inode = NULL;
+repeat:
hlist_for_each (node, head) {
prefetch(node->next);
inode = list_entry(node, struct inode, i_hash);
@@ -513,8 +514,7 @@ static struct inode * find_inode_fast(st
continue;
if (inode->i_state & (I_FREEING|I_CLEAR)) {
__wait_on_freeing_inode(inode);
- node = head->first;
- continue;
+ goto repeat;
}
break;
}
@@ -1253,11 +1253,9 @@ void __wait_on_freeing_inode(struct inod
spin_unlock(&inode_lock);
schedule();
remove_wait_queue(wq, &wait);
- current->state = TASK_RUNNING;
spin_lock(&inode_lock);
}
-
void wake_up_inode(struct inode *inode)
{
wait_queue_head_t *wq = i_waitq_head(inode);
_
next prev parent reply other threads:[~2003-05-09 22:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-08 1:44 Neil Brown
2003-05-08 20:43 ` Jan Harkes
2003-05-09 4:36 ` Neil Brown
2003-05-09 8:06 ` David Woodhouse
2003-05-09 22:24 ` Andrew Morton [this message]
2003-05-12 0:41 ` 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=20030509152410.39ede4b0.akpm@digeo.com \
--to=akpm@digeo.com \
--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®