From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: Daniel Micay <danielmicay@gmail.com>,
Kees Cook <keescook@chromium.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-kernel@vger.kernel.org
Subject: [PATCH] objtool: Add fortify_panic as __noreturn function
Date: Thu, 15 Jun 2017 08:20:35 -0500 [thread overview]
Message-ID: <1497532835-32704-1-git-send-email-jpoimboe@redhat.com> (raw)
From: Kees Cook <keescook@chromium.org>
CONFIG_FORTIFY_SOURCE implements fortify_panic() as a __noreturn function,
so objtool needs to know about it too.
Suggested-by: Daniel Micay <danielmicay@gmail.com>
Signed-off-by: Kees Cook <keescook@chromium.org>
Tested-by: Stephen Rothwell <sfr@canb.auug.org.au>
Signed-off-by: Josh Poimboeuf <jpoimboe@redhat.com>
---
tools/objtool/builtin-check.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/tools/objtool/builtin-check.c b/tools/objtool/builtin-check.c
index 282a60368b14..5f66697fe1e0 100644
--- a/tools/objtool/builtin-check.c
+++ b/tools/objtool/builtin-check.c
@@ -192,7 +192,8 @@ static int __dead_end_function(struct objtool_file *file, struct symbol *func,
"complete_and_exit",
"kvm_spurious_fault",
"__reiserfs_panic",
- "lbug_with_loc"
+ "lbug_with_loc",
+ "fortify_panic",
};
if (func->bind == STB_WEAK)
--
2.7.4
--
Kees Cook
Pixel Security
next reply other threads:[~2017-06-15 13:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-15 13:20 Josh Poimboeuf [this message]
2017-06-16 8:56 ` [tip:core/urgent] objtool: Add fortify_panic as __noreturn function tip-bot for Kees Cook
-- strict thread matches above, loose matches on Subject: below --
2017-06-15 2:18 [PATCH] " Kees Cook
2017-06-15 4:05 ` Stephen Rothwell
2017-06-15 4:26 ` Stephen Rothwell
2017-06-15 4:49 ` Daniel Micay
2017-06-15 5:07 ` Stephen Rothwell
2017-06-15 5:05 ` Stephen Rothwell
2017-06-15 13:14 ` 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=1497532835-32704-1-git-send-email-jpoimboe@redhat.com \
--to=jpoimboe@redhat.com \
--cc=danielmicay@gmail.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=sfr@canb.auug.org.au \
/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).