From: Peter Zijlstra <peterz@infradead.org>
To: Rob Landley <rob@landley.net>
Cc: Josh Poimboeuf <jpoimboe@redhat.com>,
Masahiro Yamada <masahiroy@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Andrii Nakryiko <andrii@kernel.org>
Subject: Re: Commit 0d989ac2c90b broke my x86-64 build.
Date: Mon, 25 Oct 2021 11:04:33 +0200 [thread overview]
Message-ID: <YXZzIUqdWW9wwlpr@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <66ed460c-ac48-2b5a-e8e4-07613cf69ab0@landley.net>
On Sun, Oct 24, 2021 at 09:51:45PM -0500, Rob Landley wrote:
> > Unfortunately I think CONFIG_STACK_VALIDATION is no longer optional on
> > x86-64 these days, because of static calls and retpolines.
>
> Does it need stack validation, or just a frame unwinder?
static_calls rely on objtool to find all "call __SCT*" instructions and
write their location in a .static_call_sites section.
The having of static calls is not optional on x86_64, and I have zero
interest in trying to work out what not having static_call() does, or to
maintain that option.
We have too damn many daft configurations as is.
next prev parent reply other threads:[~2021-10-25 9:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-24 6:36 Commit 0d989ac2c90b broke my x86-64 build Rob Landley
2021-10-24 18:13 ` Masahiro Yamada
2021-10-24 19:27 ` Josh Poimboeuf
2021-10-25 2:51 ` Rob Landley
2021-10-25 9:04 ` Peter Zijlstra [this message]
2021-10-25 14:46 ` Josh Poimboeuf
2021-10-25 14:56 ` Peter Zijlstra
2021-10-25 18:59 ` Josh Poimboeuf
2021-10-25 20:01 ` Peter Zijlstra
2021-10-26 3:33 ` Josh Poimboeuf
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=YXZzIUqdWW9wwlpr@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=andrii@kernel.org \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=rob@landley.net \
/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;
as well as URLs for NNTP newsgroup(s).