linux-kernel - Re: building in 32bit chroot on x86_64 host broken

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:   Tue, 5 Jun 2018 21:11:01 +0259
From:   Thomas Backlund <tmb@...eia.org>
To:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
CC:     Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: building in 32bit chroot on x86_64 host broken - IGNORE

Den 2018-06-05 kl. 20:52, skrev Thomas Backlund:
> 
> I have a 32bit x86 and a 64bit x86_64 install on the system.
> 
> With linux source up to 4.16.x I could do:
> 
> setarch i686 (or use command linux32)
> chroot /path/to/32bit/
> (/dev, /proc, /sys, /run is bind mounted in the chroot)
> 
> Then I could build a 32bit kernel in the chroot without booting the 
> 32bit system...
> 
> (host is running a 4.14 longterm kernel)
> 
> but building from 4.17 source in the chroot I get:
> 
> 
> $ uname -m
> i686
> $ make oldconfig
> scripts/kconfig/conf  --oldconfig Kconfig
> *
> * Restart config...
> *
> *
> * Linux/x86 4.17.0 Kernel Configuration
> *
> 64-bit kernel (64BIT) [Y/n/?] (NEW)
> 
> 
> 
> 
> So it does not pick up 32bit anymore ...
> 
> Is this intentional ? If so, why ? If not, how can I fix it ?
> 


Never mind...

For some reason I seem to have lost this  in the .config update to 4.17:

# CONFIG_64BIT is not set


Re-adding it restores proper behaviour...

Sorry for the noise...

--
Thomas