From: Martin Steigerwald <martin@lichtvoll.de>
To: Sven Joachim <svenjoac@gmx.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: Linux 4.16-rc4
Date: Mon, 05 Mar 2018 11:05:16 +0100 [thread overview]
Message-ID: <5552043.iprGPZeTD1@merkaba> (raw)
In-Reply-To: <878tb7eyf8.fsf@turtle.gmx.de>
Hi Sven.
Sven Joachim - 05.03.18, 09:09:
> On 2018-03-04 15:15 -0800, Linus Torvalds wrote:
> > Hmm. A reasonably calm week - the biggest change is to the 'kvm-stat'
> > tool, not any actual kernel files.
> >
> > But there's small changes all over, with architecture updates (x86,
> > s390, arm, parisc) and drivers (media, md, gpu, sound) being the bulk
> > of it. But there's some filesystem fixes (mostly btrfs),
> > documentation updates etc too.
> >
> > Go test,
>
> Huh, this version does not build for me:
>
> ,----
>
> | CALL scripts/checksyscalls.sh
> | DESCEND objtool
> | CC /usr/local/src/linux/tools/objtool/check.o
> |
> | In file included from check.c:26:0:
> | check.c: In function 'read_retpoline_hints':
> | warn.h:57:3: error: format '%ld' expects argument of type 'long int', but
> | argument 5 has type 'unsigned int' [-Werror=format=]|
> | "%s: warning: objtool: " format "\n", \
> | ^
> |
> | check.c:1135:3: note: in expansion of macro 'WARN'
> |
> | WARN("retpoline_safe size mismatch: %d %ld", sec->len, sizeof(unsigned
> | long)); ^~~~
> |
> | check.c:1135:44: note: format string is defined here
> |
> | WARN("retpoline_safe size mismatch: %d %ld", sec->len, sizeof(unsigned
> | long));|
> | ~~^
> | %d
> |
> | cc1: all warnings being treated as errors
> | mv: cannot stat '/usr/local/src/linux/tools/objtool/.check.o.tmp': No such
> | file or directory /usr/local/src/linux/tools/build/Makefile.build:96:
> | recipe for target '/usr/local/src/linux/tools/objtool/check.o' failed
> | make[3]: *** [/usr/local/src/linux/tools/objtool/check.o] Error 1
>
> `----
>
> This might be because I still use a 32-bit userland with a 64-bit
> kernel.
Building just fine here with a 64-bit userland on Debian Sid and also working
just fine, so far:
% cat /proc/version
Linux version 4.16.0-rc4-tp520-btrfstrim+ (martin@merkaba) (gcc version 7.3.0
(Debian 7.3.0-5)) #42 SMP PREEMPT Mon Mar 5 10:22:42 CET 2018
Of course a build failure may be triggered by different configuration or any
number of other reasons than using 32-bit userland.
Retpoline protection is active here:
% grep . /sys/devices/system/cpu/vulnerabilities/*
/sys/devices/system/cpu/vulnerabilities/meltdown:Mitigation: PTI
/sys/devices/system/cpu/vulnerabilities/spectre_v1:Mitigation: __user pointer
sanitization
/sys/devices/system/cpu/vulnerabilities/spectre_v2:Mitigation: Full generic
retpoline
Thanks,
--
Martin
next prev parent reply other threads:[~2018-03-05 10:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-04 23:15 Linus Torvalds
2018-03-05 8:09 ` Sven Joachim
2018-03-05 10:05 ` Martin Steigerwald [this message]
2018-03-05 10:17 ` Peter Zijlstra
2018-03-05 13:38 ` Josh Poimboeuf
2018-03-05 17:12 ` Peter Zijlstra
2018-03-05 17:20 ` Sven Joachim
2018-03-05 17:58 ` Linux 4.16: Reported regressions as of Monday, 2018-03-05 (Was: Linux 4.16-rc4) Thorsten Leemhuis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5552043.iprGPZeTD1@merkaba \
--to=martin@lichtvoll.de \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=svenjoac@gmx.de \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®