linux-kernel - Re: building in 32bit chroot on x86

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: <67595efc-410d-7517-d788-eb3c4d2d7129@mageia.org>
Date:   Thu, 7 Jun 2018 22:48:11 +0259
From:   Thomas Backlund <tmb@...eia.org>
To:     Linus Torvalds <torvalds@...ux-foundation.org>
CC:     Masahiro Yamada <yamada.masahiro@...ionext.com>,
        Ulf Magnusson <ulfalizer@...il.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: building in 32bit chroot on x86_64 host broken


Den 2018-06-07 kl. 22:40, skrev Linus Torvalds:
> On Thu, Jun 7, 2018 at 12:35 PM Thomas Backlund <tmb@...eia.org> wrote:
>> I can work around it for now (or keep the revert in our kernel builds
>> for now) until it gets properly fixed...
> So rather than doing the revert, it's probably better if  your
> workaround just does
>
>     make ARCH=i386 oldconfig
>
> (or maybe even just a "export ARCH=i386" in the environment)
>
> That should get you to continue to otherwise do the same thing.
>
> And if it turns out that your flow is the *only* one affected by this,
> and nobody else complains, maybe we can just say "yeah, slight change
> in build rules, easy to work around" and leave it at that.
>
>                  Linus

Yeah, I can live with that too :)

I just wanted to point out the regression in case it was not (sort of) 
intentional...

--
Thomas