[lkml]   [1998]   [Sep]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: 2.1.120 broken on P5 SMP machines + fix
In article <>, (Thomas Bogendoerfer) writes:
> I'm not sure, but it looks like the F00F workaround gets only enabled for
> one CPU, when we do smp_begin() before check_bugs(). So it makes sense,
> when people see that the first start of a f00f trigger program gives
> illegal instruction while the second one hangs the machine. When we do

Thanks for the patch. I've applied it, because otherwise 2.1.120 won't boot
on my machine and gives an Oops during boot (My machine: dual P100 & HX
chipsset, SMP kernel).

with your patch, the f00f bug is shown in cpuinfo, and the workaround is
okay if check_bugs() is executed before smp_init():

python:~/ass-src/minitools>objdump --disassemble f00f-exploit
08048074 <_start>:
8048074: f0 0f c7 c8 lock cmpxchg8b %eax

You can execute this program without problems:

Illegal instruction (core dumped)
Illegal instruction (core dumped)
and so on...



Linux, WinNT and MS-DOS. The Good, The Bad and The Ugly
Carsten Gross
Wohnheim Heilmeyersteige Sebastian Kneipp Weg 6, 89075 Ulm

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:44    [W:0.044 / U:2.036 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site