Subject: Re: Removing I386_CPU from GENERIC and INSTALL
To: Frank van der Linden <fvdl@netbsd.org>
From: Jason Thorpe <thorpej@shagadelic.org>
List: port-i386
Date: 10/31/2006 09:32:29
On Oct 31, 2006, at 6:16 AM, Frank van der Linden wrote:

> Yes. For example, plain i386 CPUs haven't worked correctly with NFS  
> for
> quite a while now.  Since UBC was merged, to be specific, since the
> lack of protection check on copy to/from user messes up NFS: NFS marks
> pages that need to be committed (pushed out to the server) with
> PG_NEEDCOMMIT, and then sets them to read-only. A plain i386 will not
> notice the write fault when these pages are written to again, leading
> to possible data corruption. The fact that noone had noticed this,
> leads me to believe that noone uses a plain i386 anymore. I threw
> away my last plain i386 last year.
>
> So, yes to both.

So, it seems like it would be possible to fix this for the i386 case  
by completely revoking the mapping, yes?

-- thorpej