lkml.org 
[lkml]   [2004]   [Sep]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectQ: bugs in generic_forget_inode()?
Hello,

1. I found that generic_forget_inode() calls write_inode_now() dropping
inode_lock and destroys inode after that. The problem is that
write_inode_now() can sleep and during this sleep someone can find inode
in the hash, w/o I_FREEING state and with i_count = 0.

If such inode will be iget'ed, then it will be iput'ed once more later
messing with the current iput(). So the inode can be cleared and
destroyed twice.

2. Why there is no wake_up_inode() in generic_forget_inode() like in
generic_delete_inode()? Looks like it is missing...

is it bugs in generic_forget_inode()?

Kirill

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 14:05    [W:0.292 / U:0.428 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site