linux-kernel - Re: aesbs-core.S

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: <CAKv+Gu-+FZ=mYc7pMWuFTboPpXN+a8Xj+NO7kqo_xVbZzQJwJw@mail.gmail.com>
Date:	Tue, 30 Sep 2014 18:26:19 +0200
From:	Ard Biesheuvel <ard.biesheuvel@...aro.org>
To:	Christoph Hellwig <hch@...radead.org>
Cc:	Nicolas Pitre <nico@...aro.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Nicholas Mc Guire <der.herr@...r.at>
Subject: Re: aesbs-core.S_shipped?

On 30 September 2014 17:50, Christoph Hellwig <hch@...radead.org> wrote:
> Hi Ard,
>
> can you explain me why arch/arm/crypto/aesbs-core.S_shipped
> is a _shipped file? I can't find any reason why it should be,
> it's a normal .S file in every way as far as I can tell.

It is generated by aesbs-core.pl, and Russell preferred including it
as a _shipped file rather than generating it from the perl script on
each build. (Note that the Perl script is kept in sync with OpenSSL,
i.e., the goal is to be able to generate the kernel .S and the OpenSSL
userland .S from the same script)

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