From: tip-bot for Kees Cook <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: mingo@kernel.org, sfr@canb.auug.org.au, hpa@zytor.com,
danielmicay@gmail.com, keescook@chromium.org,
linux-kernel@vger.kernel.org, jpoimboe@redhat.com,
peterz@infradead.org, tglx@linutronix.de,
torvalds@linux-foundation.org
Subject: [tip:core/urgent] objtool: Add fortify_panic as __noreturn function
Date: Fri, 16 Jun 2017 01:56:03 -0700 [thread overview]
Message-ID: <tip-92b0a1416be587b87c8ff489b6a74fd929048ca7@git.kernel.org> (raw)
In-Reply-To: <1497532835-32704-1-git-send-email-jpoimboe@redhat.com>
Commit-ID: 92b0a1416be587b87c8ff489b6a74fd929048ca7
Gitweb: http://git.kernel.org/tip/92b0a1416be587b87c8ff489b6a74fd929048ca7
Author: Kees Cook <keescook@chromium.org>
AuthorDate: Thu, 15 Jun 2017 08:20:35 -0500
Committer: Ingo Molnar <mingo@kernel.org>
CommitDate: Fri, 16 Jun 2017 10:50:59 +0200
objtool: Add fortify_panic as __noreturn function
CONFIG_FORTIFY_SOURCE=y implements fortify_panic() as a __noreturn function,
so objtool needs to know about it too.
Suggested-by: Daniel Micay <danielmicay@gmail.com>
Tested-by: Stephen Rothwell <sfr@canb.auug.org.au>
Signed-off-by: Kees Cook <keescook@chromium.org>
Signed-off-by: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Link: http://lkml.kernel.org/r/1497532835-32704-1-git-send-email-jpoimboe@redhat.com
Signed-off-by: Ingo Molnar <mingo@kernel.org>
---
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 282a603..5f66697f 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)
prev parent reply other threads:[~2017-06-16 9:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-15 13:20 [PATCH] objtool: Add fortify_panic as __noreturn function Josh Poimboeuf
2017-06-16 8:56 ` tip-bot for Kees Cook [this message]
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=tip-92b0a1416be587b87c8ff489b6a74fd929048ca7@git.kernel.org \
--to=tipbot@zytor.com \
--cc=danielmicay@gmail.com \
--cc=hpa@zytor.com \
--cc=jpoimboe@redhat.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=sfr@canb.auug.org.au \
--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