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]

Date:   Fri, 8 Jun 2018 11:12:27 +0200
From:   Michal Kubecek <mkubecek@...e.cz>
To:     Linus Torvalds <torvalds@...ux-foundation.org>
Cc:     tmb@...eia.org, 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

On Thu, Jun 07, 2018 at 12:40:30PM -0700, Linus Torvalds wrote:
> 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.

Not the only one, we hit the same problem when building openSUSE
packages (4.17-rc1) but we resolved it by always setting ARCH:

  https://github.com/openSUSE/kernel-source/commit/fb21b7321ab5

It also revealed that we forgot to pass MAKE_ARGS to other phases of RPM
build process so we don't have reason to complain.

Michal Kubecek