linux-kernel - Re: soft lockup when passing vvar address to write(2)

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: <alpine.DEB.2.11.1603050927430.3686@nanos>
Date:	Sat, 5 Mar 2016 09:28:10 +0100 (CET)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Andy Lutomirski <luto@...capital.net>
cc:	Rasmus Villemoes <linux@...musvillemoes.dk>,
	Andy Lutomirski <luto@...nel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	X86 ML <x86@...nel.org>
Subject: Re: soft lockup when passing vvar address to write(2)

On Fri, 4 Mar 2016, Andy Lutomirski wrote:
> Thomas, I still think we should consider just deleting the HPET vclock
> code and accept the syscall overhead on systems that are stuck using
> HPET.  If fast syscalls are available (which should include every
> system with HPET, unless there are some 32-bit AMD systems lying
> around), then the overhead in a syscall is *tiny* compared to the code
> of the HPET read itself.

No objection from my side, really.

Thanks,

	tglx