[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170726195543.hxyb5h4smx5rskzg@treble>
Date: Wed, 26 Jul 2017 14:55:43 -0500
From: Josh Poimboeuf <jpoimboe@...hat.com>
To: Kees Cook <keescook@...omium.org>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Daniel Micay <danielmicay@...il.com>,
Dan Williams <dan.j.williams@...el.com>,
Mika Westerberg <mika.westerberg@...ux.intel.com>,
Al Viro <viro@...iv.linux.org.uk>,
David Howells <dhowells@...hat.com>,
Heikki Krogerus <heikki.krogerus@...ux.intel.com>,
Bjorn Helgaas <bhelgaas@...gle.com>,
Arnd Bergmann <arnd@...db.de>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Mauro Carvalho Chehab <mchehab@...nel.org>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] fortify: Use WARN instead of BUG for now
On Wed, Jul 26, 2017 at 11:52:19AM -0700, Kees Cook wrote:
> --- a/tools/objtool/check.c
> +++ b/tools/objtool/check.c
> @@ -156,7 +156,7 @@ static int __dead_end_function(struct objtool_file *file, struct symbol *func,
> "kvm_spurious_fault",
> "__reiserfs_panic",
> "lbug_with_loc",
> - "fortify_panic",
> + "fortify_overflow",
> };
If the function is no longer '__noreturn' then this entry needs to be
removed from the global_noreturns list.
--
Josh
Powered by blists - more mailing lists