> > This is a known problem, it is pretty much similar to what happened under 2.0
> > for all all architectures, not just the i386 and one of reasons for the new
> > user space access stuff introduced from 2.1.4 on. Now that only the 386 is still
> > affected just nobody bothered because on the 386 there are other funnies left
> > which may make running a system used by possibly hostile users a bad idea.
>
> s/386/some very early stepping 386, which are only a small fraction
> of the existing 386ers/.
>
> So it is really not a big problem.
Afaik, even very modern 386s contain popad bug which allows any user
to lock processor hard. There is even check for that bug in asm/bugs.h
(by me :-).
Pavel
PS: My amd 386/40 certainly has popad bug.
-- I'm really pavel@atrey.karlin.mff.cuni.cz. Pavel Look at http://atrey.karlin.mff.cuni.cz/~pavel/ ;-).- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/