linux-kernel - Re: CPU_BIG_ENDIAN in generic code

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: <20170608.100222.1573468093040905016.davem@davemloft.net>
Date:   Thu, 08 Jun 2017 10:02:22 -0400 (EDT)
From:   David Miller <davem@...emloft.net>
To:     arnd@...db.de
Cc:     babu.moger@...cle.com, mpe@...erman.id.au, geert@...ux-m68k.org,
        peterz@...radead.org, mingo@...hat.com, sparclinux@...r.kernel.org,
        linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org,
        devicetree@...r.kernel.org, linux-serial@...r.kernel.org
Subject: Re: CPU_BIG_ENDIAN in generic code

From: Arnd Bergmann <arnd@...db.de>
Date: Thu, 8 Jun 2017 10:01:59 +0200

> I would also suggest adding a sanity check like

Hmm, but this will kill the build for non-fixed endian architectures
won't it?