From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-14.6 required=3.0 tests=DKIMWL_WL_MED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH, MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS,USER_IN_DEF_DKIM_WL autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id D6FF6C5B57D for ; Fri, 5 Jul 2019 09:28:11 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 8451921852 for ; Fri, 5 Jul 2019 09:28:11 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=google.com header.i=@google.com header.b="iDK20ETp" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726980AbfGEJ2L (ORCPT ); Fri, 5 Jul 2019 05:28:11 -0400 Received: from mail-oi1-f194.google.com ([209.85.167.194]:39977 "EHLO mail-oi1-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726107AbfGEJ2K (ORCPT ); Fri, 5 Jul 2019 05:28:10 -0400 Received: by mail-oi1-f194.google.com with SMTP id w196so6696472oie.7 for ; Fri, 05 Jul 2019 02:28:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=zS8S9H9AbLZAyLr81qb94mZjTnAH3YzyDKOLBvj6lLk=; b=iDK20ETpNO7KF5Suti87dkpQGGE94gt/WqR+UuMVEAldoiGs9wASNGYTNJm/jTnsMD eHGFCv3jGE98FwKAL0+b+QgMGmDBwnJRtC0ELAXyRv8QwlYpcLcxHtdDRDa7IVfNJQsG 92wQuonQuWjRA9KSTw6S6YYrlfM7n3KLQNPLW/aSm3ILK805vtgd63hUPfqzk3eDWkW8 nR3/asQvqhHOVQM0fjUCMZr+xHVQMIlo8bN07BzmFdP1LwD/bfsJzHPM2Qv04C07m+iw LnIf918+wXa3gSJ3/G0W7ZoThxxOLq6qI/h4F7iJTxZi4lbV7MditpnAehJVY89Zi5sU 0nng== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=zS8S9H9AbLZAyLr81qb94mZjTnAH3YzyDKOLBvj6lLk=; b=aWBpl4rqF7OnOKOnmMeq1/KbOYPfwkfQI82cexxBsEIh5s5S2FV+EH7/rvf2fF1CFM r4Cm4WPHi7mIdCg5A9C1+BFX6Dhf7bs5ZdPTELq8kMHsiYoug+a/zn78bQSv4pYtEI1J hdkRpZPrjJqXVU5UFL9xHOYF8q8jdD63NvjiyaBXPPUQ+jvvZ1NFF6C7YKhrXC+cwaTN /ZWzQzfTkphPiRHHukqyoEn//rA8Q76wd0z68UJi0UbKjvxlQnAwtdwMK4MQRZHCLo8+ uQOGzRJqzV82b27lXzaeRuIoquHXRBfXQf1Fv+8pLvkCyUs8pAFISpPT995C7Maj7Xc7 IjZw== X-Gm-Message-State: APjAAAUrfyTztoGTahIaMr5Wh2D5LUlBCmbT7NTNDmyHgpiHSDaoAT4F FECd14jsDWDV50z+b+INmBEpHDXNDj4kdZig3Y1ZNg== X-Google-Smtp-Source: APXvYqxWPHLAHk5InL17x7b5nOFeiSVFxnFojoqcX5d9DBobJVe4cQ7uu+zZn6rxaWS+Gr+LQnhsauLWGZiQlqxrrPY= X-Received: by 2002:aca:6104:: with SMTP id v4mr1529831oib.172.1562318889763; Fri, 05 Jul 2019 02:28:09 -0700 (PDT) MIME-Version: 1.0 References: <20190705184949.13cdd021@canb.auug.org.au> In-Reply-To: <20190705184949.13cdd021@canb.auug.org.au> From: Marco Elver Date: Fri, 5 Jul 2019 11:27:58 +0200 Message-ID: Subject: Re: linux-next: build failure after merge of the akpm-current tree To: Stephen Rothwell Cc: Andrew Morton , Linux Next Mailing List , Linux Kernel Mailing List Content-Type: text/plain; charset="UTF-8" Sender: linux-next-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-next@vger.kernel.org On Fri, 5 Jul 2019 at 10:49, Stephen Rothwell wrote: > > Hi all, > > After merging the akpm-current tree, today's linux-next build (arm > multi_v7_defconfig) failed like this: > > In file included from include/linux/compiler.h:257, > from arch/arm/kernel/asm-offsets.c:10: > include/linux/kasan-checks.h:14:15: error: unknown type name 'bool' > static inline bool __kasan_check_read(const volatile void *p, unsigned int size) > ^~~~ > include/linux/kasan-checks.h:18:15: error: unknown type name 'bool' > static inline bool __kasan_check_write(const volatile void *p, unsigned int size) > ^~~~ > include/linux/kasan-checks.h:38:15: error: unknown type name 'bool' > static inline bool kasan_check_read(const volatile void *p, unsigned int size) > ^~~~ > include/linux/kasan-checks.h:42:15: error: unknown type name 'bool' > static inline bool kasan_check_write(const volatile void *p, unsigned int size) > ^~~~ > > Caused by commit > > 4bb170e54bbd ("mm/kasan: change kasan_check_{read,write} to return boolean") > > I have added the following patch for today: > > From: Stephen Rothwell > Date: Fri, 5 Jul 2019 18:44:55 +1000 > Subject: [PATCH] mm/kasan: include types.h for "bool" > > Signed-off-by: Stephen Rothwell > --- > include/linux/kasan-checks.h | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/include/linux/kasan-checks.h b/include/linux/kasan-checks.h > index 2c7f0b6307b2..53cbf0ae14b5 100644 > --- a/include/linux/kasan-checks.h > +++ b/include/linux/kasan-checks.h > @@ -2,6 +2,8 @@ > #ifndef _LINUX_KASAN_CHECKS_H > #define _LINUX_KASAN_CHECKS_H > > +#include > + > /* > * __kasan_check_*: Always available when KASAN is enabled. This may be used > * even in compilation units that selectively disable KASAN, but must use KASAN > -- > 2.20.1 > > -- > Cheers, > Stephen Rothwell Apologies for the breakage -- thanks for the fix! Shall I send a v+1 or will your patch persist?