Date: Fri, 23 Jul 1999 07:53:39 +1000 From: Peter Jeremy <jeremyp@gsmx07.alcatel.com.au> To: current@FreeBSD.ORG Subject: `stale FS getpages' messages Message-ID: <99Jul23.073510est.40356@border.alcanet.com.au>
next in thread | raw e-mail | index | archive | help
I've just received the following kernel messages (running a kernel from cvs-cur 5476 - about last Thursday): vnode_pager: *** WARNING *** stale FS getpages No strategy for buffer at 0xc1c03aa8 : 0xc6168380: type VREG, usecount 3, writecount 0, refcount 0, flags (VOBJBUF) tag VT_PROCFS, type 5, pid 36, mode 0x180, flags 0 : 0xc6168380: type VREG, usecount 3, writecount 0, refcount 0, flags (VOBJBUF) tag VT_PROCFS, type 5, pid 36, mode 0x180, flags 0 vnode_pager_getpages: I/O read error vm_fault: pager read error, pid 39554 (sylk1) pid 39554 (sylk1), uid 0: exited on signal 11 (core dumped) Looking at my core dump, it seems that sylk1 had mmap()d /proc/36/regs (FWIW, this is mfs) and caused the problem by trying to de-reference the first word of the mmap'd region. Accessing the data using a read(2) works correctly. I believe this behaviour is undesirable. If I can successfully mmap() a region (the actual parameters were PROT_READ, MAP_SHARED), I should be able to read the mmap'd region. Unfortunately, I don't understand the filesystem/vnode layering well enough to be able to easily identify what's missing. Peter 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?99Jul23.073510est.40356>