linux-kernel - Re: [BUGFIX] Fix AES-NI CTR optimization compiling failure with gas 2.16.1

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: <4B99FF0A.1030700@redhat.com>
Date:	Fri, 12 Mar 2010 10:44:58 +0200
From:	Avi Kivity <avi@...hat.com>
To:	David Miller <davem@...emloft.net>
CC:	ying.huang@...el.com, akpm@...ux-foundation.org,
	herbert@...dor.apana.org.au, linux-kernel@...r.kernel.org,
	linux-crypto@...r.kernel.org
Subject: Re: [BUGFIX] Fix AES-NI CTR optimization compiling failure with gas
 2.16.1

On 03/12/2010 10:42 AM, David Miller wrote:
> From: Avi Kivity<avi@...hat.com>
> Date: Fri, 12 Mar 2010 10:37:33 +0200
>
>    
>> Eventually you'll port the entire assembler into macros, as
>> instructions are introduced more frequently that people upgrade their
>> assemblers.  Maybe we should disable the new features and warn people
>> (and distros) to upgrade their tools instead.
>>      
> I totally and completely disagree.
>
> It would have taken more than a year to get Niagara cpu support out to
> people if I had done what you are suggesting.
>    

Strange, that people can install a new kernel, but not a new assembler.

> And here we're talking about one instruction in one specialized case
> in a very piece of crypto module assembler.
>    

If it were one place, I'd agree, but there are more.  kvm for example 
also uses .byte instead of the actual instructions.

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.

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