linux-kernel - Re: FP in kernelspace

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: <Pine.LNX.4.61.0607310110180.11084@yvahk01.tjqt.qr>
Date:	Mon, 31 Jul 2006 01:11:51 +0200 (MEST)
From:	Jan Engelhardt <jengelh@...ux01.gwdg.de>
To:	Avi Kivity <avi@...o.co.il>
cc:	Jiri Slaby <jirislaby@...il.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: FP in kernelspace

>> > kernel_fpu_begin();
>> > c = d * 3.14;
>> > kernel_fpu_end();
>> 
>> static inline void kernel_fpu_begin() {
>> ...
>> preempt_disable();
>> ...
>> }
>> 
> Is the kernel allowed to clobber userspace's sse registers?

As long as you save and restore it properly, and make it look like to all 
other threads that nothing happened, you are (I hope) free to do anything.

> What about interrupt code?

You do not want to go there...

> xor.h at least appears to save the sse state before use.
>
> -- 
> Do not meddle in the internals of kernels, for they are subtle and quick to
> panic.

Follow that advice, don't do FP. But OTOH......<long dots> there is already 
an SSE player in the kernel: drivers/md/raid6sse*.c


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