linux-kernel - Re: use of setjmp/longjmp in x86 emulator.

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]

Message-ID: <4B8C4032.7080703@zytor.com>
Date:	Mon, 01 Mar 2010 14:31:14 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Zachary Amsden <zamsden@...hat.com>
CC:	Gleb Natapov <gleb@...hat.com>, linux-kernel@...r.kernel.org,
	mingo@...e.hu, avi@...hat.com, mtosatti@...hat.com
Subject: Re: use of setjmp/longjmp in x86 emulator.

On 03/01/2010 11:18 AM, Zachary Amsden wrote:
> 
> It's going to be ugly to emulate segmentation, NX and write protect 
> support without hardware to do this checking for you, but it's just what 
> you have to do in this slow path - tedious, fully specified emulation.
> 
> Just because it's tedious doesn't mean we need to use setjmp / longjmp.  
> Throw / catch might be effective, but it's still pretty bizarre to do 
> tricks like that in C.
> 

Well, setjmp/longjmp really is not much more than exception handling in C.

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