From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752421AbdHAUo3 (ORCPT ); Tue, 1 Aug 2017 16:44:29 -0400 Received: from mail-oi0-f52.google.com ([209.85.218.52]:36573 "EHLO mail-oi0-f52.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752152AbdHAUo1 (ORCPT ); Tue, 1 Aug 2017 16:44:27 -0400 MIME-Version: 1.0 In-Reply-To: References: <20170801162511.39fa58ad@canb.auug.org.au> From: Arnd Bergmann Date: Tue, 1 Aug 2017 22:44:26 +0200 X-Google-Sender-Auth: bsZ0NsTHpfWXphOsPqEd8aM_tKw Message-ID: Subject: Re: linux-next: build failure after merge of the akpm tree To: Kees Cook Cc: Stephen Rothwell , Andrew Morton , Linux-Next Mailing List , Linux Kernel Mailing List Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Aug 1, 2017 at 8:40 PM, Kees Cook wrote: >> >> I don't know why this has turned up now. I have just left it broken >> for now and would appreciate any fix. > > Thanks for the heads-up! I'm not sure why this suddenly appeared > either, but Arnd has sent a patch for this now. The main difference I see that can impact gcc's optimization steps is the unreachable() that was there in BUG() but is absent in WARN(). It's possible that the compiler decided that the entire code path leading up to the unreachable() couldn't happen, so it dropped the __read_overflow2() call as well. Arnd