From: Kees Cook <keescook@chromium.org>
To: linux-kernel@vger.kernel.org
Cc: Josh Poimboeuf <jpoimboe@redhat.com>,
Daniel Micay <danielmicay@gmail.com>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: [PATCH] objtool: Add fortify_panic as __noreturn function
Date: Wed, 14 Jun 2017 19:18:51 -0700 [thread overview]
Message-ID: <20170615021851.GA83998@beast> (raw)
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>
Cc: 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 2:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-15 2:18 Kees Cook [this message]
2017-06-15 4:05 ` [PATCH] objtool: Add fortify_panic as __noreturn function 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
-- strict thread matches above, loose matches on Subject: below --
2017-06-15 13:20 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=20170615021851.GA83998@beast \
--to=keescook@chromium.org \
--cc=danielmicay@gmail.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.