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=-8.6 required=3.0 tests=DKIMWL_WL_MED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_IN_DEF_DKIM_WL autolearn=no 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 73361C433E0 for ; Tue, 23 Jun 2020 10:09:21 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 435C0206D4 for ; Tue, 23 Jun 2020 10:09:21 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=google.com header.i=@google.com header.b="pCU7BT0t" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1732244AbgFWKJT (ORCPT ); Tue, 23 Jun 2020 06:09:19 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42220 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728265AbgFWKJT (ORCPT ); Tue, 23 Jun 2020 06:09:19 -0400 Received: from mail-oi1-x242.google.com (mail-oi1-x242.google.com [IPv6:2607:f8b0:4864:20::242]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0C34AC061573 for ; Tue, 23 Jun 2020 03:09:19 -0700 (PDT) Received: by mail-oi1-x242.google.com with SMTP id c194so18375023oig.5 for ; Tue, 23 Jun 2020 03:09:19 -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=rU2hdhGD7fNtW6Y+12AGojPtiGkpRBwEsJIOODw6oSk=; b=pCU7BT0tDtwCvaiAm4xPhpb1ZoO7AvlAMIiGWxQqFb9kiDu3fiYmT+Y1yteEWeSc8M N1dfj19zTPci8X2KQTYhNOI719d7om5Q3LDRcDayt/Or/0DdPiNQ/Yu2eFHh7B9bQAk/ yhZILXAelpJfhCF34X76NuMC0NO+V2pFFftCrfwqJ/DNjQ7EzfIAYp21TpEW3BncSE2u ADuFCObQQiM6P0oROGxUywcr1Xmu6rKUJ6P/+pTuhSyUWRhVizBeUVr3R7/6w9hGV40t t/q9hOcDfwTdpaOkVqoy+jWDDyPuLd1gcisny5nVn5726xXHQfo6b6FjfE1K4dSGIqJ/ 7rUw== 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=rU2hdhGD7fNtW6Y+12AGojPtiGkpRBwEsJIOODw6oSk=; b=DC1JqkdHcYo4GblBpDEEDLOHFjJrv3OPa9SUeih0xjOiNi8aK5Pi6/8fjKE5l4peSt PF3zAQsGltiEG8FI8961RRnj77AmXFVUjLFLCFu3pWU6RWA2ohemxr588ljZxTMPSd8c OrrJK57H0XQjOgzRBH1lsDREnbtnQ9HlWqV/ae4D+MjW0NMEogJiZcK0GFbTNHL1iiAj uagRhmmUE3VhxwIhIvaO1/YTwk46tnRcUObZbe26eV7JN78GMzdkJNgjI1Pbsc7LWFTp vGDebOZBXr+0IML6l+KaM0KCnJhR+UMCzr4jzjIzUp4PeEHrxwAdH75D0RterxKQRXuh MIJw== X-Gm-Message-State: AOAM533uv/6Jb1YsU4G379vLYE24K9Rk2Bc+3NsnKNboqRg+NbPy2HqV xGHiypPbtIMnGZ3v5mX1jhfNfDCTY/8xZG62Mw5c2g== X-Google-Smtp-Source: ABdhPJyLbqT3YNW3hb8nC+z6sAupP/viLWv3tDVCgY+urTIUfRq5q9195OLwSA9zcAZDtENjTwGGr82qLFRD3gKojPU= X-Received: by 2002:aca:530e:: with SMTP id h14mr15692305oib.172.1592906958117; Tue, 23 Jun 2020 03:09:18 -0700 (PDT) MIME-Version: 1.0 References: <000000000000c25ce105a8a8fcd9@google.com> <20200622094923.GP576888@hirez.programming.kicks-ass.net> <20200623124413.08b2bd65@canb.auug.org.au> <20200623093230.GD4781@hirez.programming.kicks-ass.net> In-Reply-To: <20200623093230.GD4781@hirez.programming.kicks-ass.net> From: Marco Elver Date: Tue, 23 Jun 2020 12:09:06 +0200 Message-ID: Subject: Re: linux-next build error (9) To: Peter Zijlstra Cc: Stephen Rothwell , syzbot , Borislav Petkov , "H. Peter Anvin" , Jim Mattson , joro@8bytes.org, kvm@vger.kernel.org, LKML , Linux Next Mailing List , Ingo Molnar , Paolo Bonzini , sean.j.christopherson@intel.com, syzkaller-bugs , Thomas Gleixner , vkuznets@redhat.com, wanpengli@tencent.com, "the arch/x86 maintainers" Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 23 Jun 2020 at 11:32, Peter Zijlstra wrote: > > On Tue, Jun 23, 2020 at 12:44:13PM +1000, Stephen Rothwell wrote: > > Hi Peter, > > > > On Mon, 22 Jun 2020 11:49:23 +0200 Peter Zijlstra wrote: > > > > Hurmph, I though that was cured in GCC >= 8. Marco? > > > > So what causes this? Because we got a couple of these in our s390 builds last night as well. > > This is KASAN's __no_sanitize_address function attribute. Some GCC > versions are utterly wrecked when that function attribute is combined > with inlining. It wants to have matching attributes for the function > being inlined and function it is inlined into -- hence the function > attribute mismatch. > > > kernel/locking/lockdep.c:805:1: error: inlining failed in call to always_inline 'look_up_lock_class': function attribute mismatch > > include/linux/debug_locks.h:15:28: error: inlining failed in call to always_inline '__debug_locks_off': function attribute mismatch > > > > s390-linux-gcc (GCC) 8.1.0 / GNU ld (GNU Binutils) 2.30 > > *groan*... So supposedly it was supposed to work on GCC-8 and later, see > commit 7b861a53e46b6. But now it turns out there's some later versions > that fail too. > > I suppose the next quest is finding a s390 compiler version that works > and then bumping the version test in the aforementioned commit. I'm trying to figure out by inspecting GCC changelogs which version and which arch is actually good. Thanks, -- Marco