H. Peter Anvin writes: > This would leave no way (without introducing new interfaces) to write, > for example, the boot block on an ext2 filesystem. Note that the > bootblock (defined as the first 1024 bytes) is not actually used by > the filesystem, although depending on the block size it may share a > block with the superblock (if blocksize > 1024). The lack of coherency would screw this up anyway, doesn't it? You have a block device, soon to be in the page cache, and a superblock, also soon to be in the page cache. LILO writes to the block device, while the ext2 driver updates the superblock. Whatever gets written out last wins, and the other is lost. - 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/
- Re: Getting FS access events Richard Gooch
- Re: Getting FS access events Linus Torvalds
- Re: Getting FS access events Richard Gooch
- Re: Getting FS access events Alexander Viro
- Re: Getting FS access events Daniel Phillips
- Re: Getting FS access events Alexander Viro
- Re: Getting FS access events Daniel Phillips
- Re: Getting FS access events Linus Torvalds
- Re: Getting FS access events Anton Altaparmakov
- Re: Getting FS access events H. Peter Anvin
- Re: Getting FS access events Albert D. Cahalan
- Re: Getting FS access events H. Peter Anvin
- Re: Getting FS access events Anton Altaparmakov
- Re: Getting FS access events H. Peter Anvin
- Re: Getting FS access events Anton Altaparmakov
- Re: Getting FS access events H. Peter Anvin
- Re: Getting FS access events Craig Milo Rogers
- Re: Getting FS access events Pavel Machek
- Re: Getting FS access events Pavel Machek
- Re: Getting FS access events Linus Torvalds
- Re: Getting FS access events Pavel Machek