linux-kernel - Re: [PATCH FIXED] x86: only enable interrupts when kernel state has been set up

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20080325105559.GA3729@elte.hu>
Date:	Tue, 25 Mar 2008 11:56:00 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Jeremy Fitzhardinge <jeremy@...p.org>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH FIXED] x86: only enable interrupts when kernel state
	has been set up


* Jeremy Fitzhardinge <jeremy@...p.org> wrote:

> The sysenter path tries to enable interrupts immediately.  
> Unfortunately this doesn't work in a paravirt environment, because not 
> enough kernel state has been set up at that point (namely, pointing 
> %fs to the kernel percpu data segment).  To fix this, defer 
> ENABLE_INTERRUPTS until after the kernel state has been set up.
>
> Unfortunately this means that we're running with interrupts disabled 
> for a while without calling the IRQ tracing code, but that can't be 
> called without setting up %fs either.
>
> [ Fix since last posting: make sure saved eflags has interrupts 
> enabled. ]

thanks Jeremy - will give it a shot.

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