From: Brendan Jackman <jackmanb@google.com>
To: Josh Poimboeuf <jpoimboe@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
Masahiro Yamada <masahiroy@kernel.org>,
Nathan Chancellor <nathan@kernel.org>,
Nicolas Schier <nicolas@fjasle.eu>
Cc: linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org,
Brendan Jackman <jackmanb@google.com>
Subject: [PATCH 0/2] objtool: Add option to fail build on vmlinux warnings
Date: Fri, 13 Dec 2024 11:31:29 +0000 [thread overview]
Message-ID: <20241213-objtool-strict-v1-0-fd388f9d971f@google.com> (raw)
This adds an option to objtool to exit with an error when it enounters
warnings.
Then, it adds a config to enable that flag on vmlinux. This enables you
to fail the build e.g. when noinstr is violated.
Signed-off-by: Brendan Jackman <jackmanb@google.com>
---
Brendan Jackman (2):
objtool: Add --fail-on-warn
kbuild: Add option to fail build on vmlinux objtool issues
lib/Kconfig.debug | 11 +++++++++++
scripts/Makefile.vmlinux_o | 1 +
tools/objtool/builtin-check.c | 6 ++++++
tools/objtool/check.c | 7 ++-----
tools/objtool/include/objtool/builtin.h | 1 +
5 files changed, 21 insertions(+), 5 deletions(-)
---
base-commit: f932fb9b40749d1c9a539d89bb3e288c077aafe5
change-id: 20241213-objtool-strict-cb9a0a75139e
Best regards,
--
Brendan Jackman <jackmanb@google.com>
next reply other threads:[~2024-12-13 11:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 11:31 Brendan Jackman [this message]
2024-12-13 11:31 ` [PATCH 1/2] objtool: Add --fail-on-warn Brendan Jackman
2024-12-14 0:36 ` Josh Poimboeuf
2024-12-16 9:55 ` Brendan Jackman
2024-12-13 11:31 ` [PATCH 2/2] kbuild: Add option to fail build on vmlinux objtool issues Brendan Jackman
2024-12-14 0:52 ` Josh Poimboeuf
2024-12-16 10:00 ` Brendan Jackman
2024-12-18 9:08 ` 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=20241213-objtool-strict-v1-0-fd388f9d971f@google.com \
--to=jackmanb@google.com \
--cc=akpm@linux-foundation.org \
--cc=jpoimboe@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=nicolas@fjasle.eu \
--cc=peterz@infradead.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