From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Rothwell Subject: Re: linux-next: build failure after merge of the akpm-current tree Date: Thu, 15 Jun 2017 12:04:06 +1000 Message-ID: <20170615120406.134205ee@canb.auug.org.au> References: <20170605170117.6a1fc15e@canb.auug.org.au> <20170615113548.3e4edcf4@canb.auug.org.au> <1497491922.1435.1.camel@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: Received: from ozlabs.org ([103.22.144.67]:49477 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751606AbdFOCEI (ORCPT ); Wed, 14 Jun 2017 22:04:08 -0400 In-Reply-To: <1497491922.1435.1.camel@gmail.com> Sender: linux-next-owner@vger.kernel.org List-ID: To: Daniel Micay Cc: Kees Cook , Andrew Morton , Linux-Next Mailing List , Linux Kernel Mailing List Hi Daniel, On Wed, 14 Jun 2017 21:58:42 -0400 Daniel Micay wrote: > > They're false positive warnings. I think objtool has a list of > __noreturn functions and needs fortify_panic added there. It's just a > warning so it doesn't need to happen immediately. There are *lots* of them, so it does need to be fixed (Linus will be very irritated if it hits his tree like that). Create a patch to objtool and get the x86 guys to Ack it? -- Cheers, Stephen Rothwell