> I didn't actually think about the sb_list stuff, but my feeling is you > should not move it unless there's a very clear reason to do so. Well, no problems. Probably safeness is of greater priority. I'll take care not to touch it. Thanks for review. -- Best Regards, Artem B. Bityuckiy, St.-Petersburg, Russia. - 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/
- References:
- [PATCH] VFS bugfix: two read_inode() calles without clear_inode() call between
- From: "Artem B. Bityuckiy" <[email protected]>
- Re: [PATCH] VFS bugfix: two read_inode() calles without clear_inode() call between
- From: Miklos Szeredi <[email protected]>
- Re: [PATCH] VFS bugfix: two read_inode() calles without clear_inode() call between
- From: "Artem B. Bityuckiy" <[email protected]>
- Re: [PATCH] VFS bugfix: two read_inode() calles without clear_inode() call between
- From: "Artem B. Bityuckiy" <[email protected]>
- Re: [PATCH] VFS bugfix: two read_inode() calles without clear_inode() call between
- From: Miklos Szeredi <[email protected]>
- [PATCH] VFS bugfix: two read_inode() calles without clear_inode() call between
- Prev by Date: Re: pci-sysfs resource mmap broken (and PATCH)
- Next by Date: [PATCH] fs/Kconfig: more consistent configuration of XFS
- Previous by thread: Re: [PATCH] VFS bugfix: two read_inode() calles without clear_inode() call between
- Next by thread: [PATCH] fix microtek.c compile failure
- Index(es):
 |