Subject: kernel mappings of shared-library pages
To: None <>
From: Richard Earnshaw <>
List: tech-kern
Date: 10/13/2001 09:51:06
While working on a fix for pr/13998 I noticed that several (maybe many) 
shared library pages seem to be permanently mapped into the kernel.  This 
is bad news on a VAC machine since such mappings tend to be always 
writable, so we must leave all such mappings of that page uncached (all 
user-space mappings are read-only).

Is this correct behaviour (that the kernel should keep a mapping of such 

If not, any idea where they may be being entered?