> > [Cyrix coma bug removed in 2.3.10-pre4]
> >
> > > May I ask why?
> >
> > Search me, with 2.3.10-pre4 applied, the exploit works again (as expected,
> > really); therefore you won't be able to run secure multi-user systems with
> > 2.3.10+.
>
> Because the fix in 2.3.10 is plain wrong, and because it can be done by
> set6x86 quite nicely anyway. That leaves the Cyrix486DLC bug to squash ;)
Alan, should not kernel at least warn that cpu is not working?
If I boot system I expect any hang to be kernel problem. Removing coma
workaround and relying on set6x86 is wrong in my eyes. At least
/proc/cpuinfo should read something like
BROKEN THIS CPU DOES NOT WORK
or something like that.
Pavel
-- The best software in life is free (not shareware)! Pavel GCM d? s-: !g p?:+ au- a--@ w+ v- C++@ UL+++ L++ N++ E++ W--- M- Y- R+- 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/