Messages in this thread | | | Date | Sat, 7 Aug 2004 16:21:34 +0200 | From | Pozsar Balazs <> | Subject | Re: [PATCH] VFS readahead bug in 2.6.8-rc[1-3] |
| |
On Sat, Aug 07, 2004 at 04:58:21AM +1000, Nick Piggin wrote: > Phillip Lougher wrote: > >Nick Piggin wrote: > > > >>On second thought, maybe not. I think your filesystem is at fault. > > > > > >No I'm not wrong here. With a read-only filesystem i_size can > >never change, there are no possible race conditions. If a too > >large index is passed it is a VFS bug. Are you suggesting I should > >start to code assuming the VFS is broken? > > > > No, I suggest you start to code assuming this interface does > what it does. I didn't say there is no bug here, but nobody > else's filesystem breaks.
Well, that might not exactly be true. We have noticed the same problem with ext2 too. Maybe I can send an example initrd image which triggers the bug on Monday.
-- Pozsar Balazs - 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/
| |