Re: innd mmap bug in 2.4.0-test12

From: Linus Torvalds (torvalds@transmeta.com)
Date: Tue Dec 26 2000 - 00:37:05 EST


On Tue, 26 Dec 2000, Chris Wedgwood wrote:

> On Mon, Dec 25, 2000 at 01:42:33AM -0800, Linus Torvalds wrote:
>
> We just don't write them out. Because right now the only thing
> that writes out dirty pages is memory pressure. "sync()",
> "fsync()" and "fdatasync()" will happily ignore dirty pages
> completely. The thing that made me overlook that simple thing in
> testing was that I was testing the new VM stuff under heavy VM
> load - to shake out any bugs.
>
> Does this mean anyone using test13-pre4 should also expect to see
> data not being flushed on shutdown?

No.

This all only matters to things that do shared writable mmap's.

Almost nothing does that. innd is (sadly) the only regular thing that uses
this, which is why it's always innd that breaks, even if everything else
works.

And even innd is often compiled to use "write()" instead of shared
mappings (it's a config option), so not even all innd's will break.

                Linus

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



This archive was generated by hypermail 2b29 : Sun Dec 31 2000 - 21:00:08 EST