linux-kernel - Re: [PATCH 0/4] Remove interrupt stack table usage from x86

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] [day] [month] [year] [list]

Date:	Sat, 27 Dec 2008 23:42:26 +0200
From:	Avi Kivity <avi@...hat.com>
To:	Ingo Molnar <mingo@...e.hu>
CC:	"H. Peter Anvin" <hpa@...or.com>, jeremy@...p.org,
	linux-kernel@...r.kernel.org, kvm@...r.kernel.org
Subject: Re: [PATCH 0/4] Remove interrupt stack table usage from x86_64	kernel
 (v2)

Ingo Molnar wrote:
> * Ingo Molnar <mingo@...e.hu> wrote:
>
>   
>> They have the following commit IDs, and they are also in tip/master:
>>
>>  921e521: x86: move NMI back to interrupt stack
>>  36ef6c9: x86: make interrupt stack switching atomic
>>  dd64891: x86: consolidate irq stack switching to a single macro
>>  955a368: x86: drop the use of the tss interrupt stack table (IST)
>>
>> I also started testing them in tip-qa.
>>     
>
> testing failed quickly, the attached config crashes. I've pushed out the 
> bad kernel to the tip/tmp.master.bad branch:
>
>  fe3aac9: Merge branch 'x86/irq'
>
> (no crashlog available - all i know that the box crashed and rebooted, 
> when booted with the bzImage built out of the attached config.)
>   

I managed to reproduce this (after several hundred million interrupts 
and several dozen million NMIs - do you run anything special on your tests?)

-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.

--
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/