Re: [PATCH] VFS bugfix: two read_inode() calles without clear_inode() call between

> Comments?
> 

On second thought a wake_up_inode() seems to be missing in
dispose_list() just before destroy_inode().  

Also I'm not sure delaying removal from i_sb_list is the right thing.
generic_delete_inode() does this before clear_inode().

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

Follow-Ups:
- Re: [PATCH] VFS bugfix: two read_inode() calles without clear_inode() call between
  - From: "Artem B. Bityuckiy" <[email protected]>

References:
- [PATCH] VFS bugfix: two read_inode() calles without clear_inode() call between
  - From: "Artem B. Bityuckiy" <[email protected]>

Prev by Date: Panic on a BIOSless machine.
Next by Date: Re: [PATCH] VFS bugfix: two read_inode() calles without clear_inode() call between
Previous by thread: Re: [PATCH] VFS bugfix: two read_inode() calles without clear_inode() call between
Next by thread: Re: [PATCH] VFS bugfix: two read_inode() calles without clear_inode() call between
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]