Re: Q: bugs in generic_forget_inode()?

[Andrew Morton]

Kirill Korotaev <dev@xxxxx> wrote:
>
> 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.

The filesystem is in the process of being unmounted (!MS_ACTIVE).  So the
question is: who is doing inode lookups against a soon-to-be-defunct
filesystem?


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