linux-kernel - Re: v2.6.27-rc7: x86: #GP on panic?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 25 Sep 2008 13:49:40 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Vegard Nossum <vegard.nossum@...il.com>
CC:	Ingo Molnar <mingo@...e.hu>, x86@...nel.org,
	linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>
Subject: Re: v2.6.27-rc7: x86: #GP on panic?

Vegard Nossum wrote:
> 
> But I don't see how the divide error could occur here:
> 
> ffffffff8103918b:       fb                      sti
> ffffffff8103918c:       49 c7 c4 80 c0 6e 81    mov    $0xffffffff816ec080,%r12
> ffffffff81039193:       f6 c3 01                test   $0x1,%bl
> ffffffff81039196:       74 27                   je     ffffffff810391bf <__do_so
> ffffffff81039198:       4c 89 e7                mov    %r12,%rdi
> ffffffff8103919b:       41 ff 14 24             callq  *(%r12)
> 
> Seems like an external interrupt happened and was delivered after the sti?
> 
> Hm. I guess it smells like a qemu bug since it's rather easily
> reproducible here and sounds strange that nobody else saw it. Is qemu
> 0.9.1.
> 

Yes, but there shouldn't be any external interrupts that could turn into 
  a divide error.  It really smells like a Qemu problem -- possibly even 
a Qemu miscompile -- to me.

Does it reproduce in KVM?

	-hpa
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/