Date: Sun, 10 Dec 2000 23:53:34 -0800 (PST) From: Matt Dillon <dillon@earth.backplane.com> To: Philipp Mergenthaler <un1i@rz.uni-karlsruhe.de> Cc: freebsd-current@freebsd.org Subject: patch #3 (was Re: panic: vm_pageout_flush: partially dirty page) Message-ID: <200012110753.eBB7rYP89514@earth.backplane.com> References: <20001210033546.A13896@rz.uni-karlsruhe.de> <200012102334.eBANYWm87853@earth.backplane.com> <20001211011119.B21036@rz.uni-karlsruhe.de> <200012110030.eBB0UdI88063@earth.backplane.com> <20001211020611.A6308@rz.uni-karlsruhe.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Phillipp. I couldn't find a quick fix so I recommend using the
very first patch I sent you that changes the KASSERT that was
causing the panic. I am comitting a slight variation of that patch to
current now and stable in two days.
The KASSERT was being a little too conservative in regards to dirty
bits that are 'beyond the file EOF'. These get set when you dirty a
mmap'd page, but only some of them get cleared when the filesystem
buffer (containing the last fragment of a file) is synced, leaving
m->dirty looking something like 0xFC. I believe the extra page cleaning
write that occurs (and has occured for the last year) is harmless
enough for now.
-Matt
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200012110753.eBB7rYP89514>