linux-kernel - Re: Merge branch 'core-objtool-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip

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:   Sun, 12 Apr 2020 01:30:34 +0800
From:   youling 257 <youling257@...il.com>
To:     Peter Zijlstra <peterz@...radead.org>
Cc:     viro@...iv.linux.org.uk, jpoimboe@...hat.com,
        linux-kernel@...r.kernel.org
Subject: Re: Merge branch 'core-objtool-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip

i build 64bit kernel on 32bit host. please fix.

2020-04-09 15:38 GMT+08:00, Peter Zijlstra <peterz@...radead.org>:
> On Thu, Apr 09, 2020 at 10:00:53AM +0800, youling 257 wrote:
>> d937a6dfc9428f470c3ce4d459c390944ddef538 caused 64bit kernel build
>> failed on 32bit userspace.
>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d937a6dfc9428f470c3ce4d459c390944ddef538
>>
>> 2020-04-08 16:13 GMT+08:00, youling 257 <youling257@...il.com>:
>> > after this merge branch, build 64bit kernel failed on 32bit userspace.
>> >
>> >
>> >   CC       tools/objtool/builtin-check.o
>> >   CC       tools/objtool/builtin-orc.o
>> > In file included from check.h:10,
>> >                  from builtin-check.c:18:
>> > elf.h: In function ‘sec_offset_hash’:
>> > elf.h:102:14: error: right shift count >= width of type
>> > [-Werror=shift-count-overflow]
>> >   102 |  oh = offset >> 32;
>> >       |              ^~
>
> Oh right; I figured it wouldn't matter since we don't do objtool for
> 32bit kernels, but I suppose you're cross building a 64bit kernel on a
> 32bit host or something daft like that?
>
> I'll go fix it.
>