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=-7.7 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED 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 07D25C433E0 for ; Tue, 12 Jan 2021 21:54:55 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id BD5BB2078E for ; Tue, 12 Jan 2021 21:54:54 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2437604AbhALVeb (ORCPT ); Tue, 12 Jan 2021 16:34:31 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59254 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2436960AbhALUdK (ORCPT ); Tue, 12 Jan 2021 15:33:10 -0500 Received: from mail-io1-xd33.google.com (mail-io1-xd33.google.com [IPv6:2607:f8b0:4864:20::d33]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 2AA92C061786 for ; Tue, 12 Jan 2021 12:32:30 -0800 (PST) Received: by mail-io1-xd33.google.com with SMTP id d9so6869099iob.6 for ; Tue, 12 Jan 2021 12:32:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=btCnt2sQ0Zcyyo8rzXgbt+j/5gYam3eBNLgnqdULuEc=; b=m49sd1VzO8+8Ko5TiXvXtt1vhA8wfYRIkrk6kPmcbmw3TF8EvzbpMkh1jp03X2tSzh znmih0gQVRM/t9w7A0oqZNlmi0XIIfDMMNIk4zwsAhk7y/iXjPsWPkopSf/03bxJKYeI r2bNTMi/fLAase/NHfI11voPsaBxTjYU2yS9SzgmGi6QCOLnECvY9gUEkXV0gH974aRm dzLpAwsxByVymcyY5BQY9KoEIEI0FdfjBXCefBXnHoYiBKikoyOgQSU1lhJaQKEAnDnT EVtaYcmmGErDpIsUZd6QEqMpRNV8Vpj3s1sL0W7SUKiY2kMjnoQP3ZDRHOdyNizf+CuS tdtw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=btCnt2sQ0Zcyyo8rzXgbt+j/5gYam3eBNLgnqdULuEc=; b=ig7sXwVW6bn8l148D8j49/LJSXrGXehffQS01TBaxRL8DraPA7uqL4X2HPciuuh/du DHwVttYrT8PqFoaSWwTx4OJJ0o7+y52np7IZlRzakhAmCKugidAUdAv/1zCWZr8Gh+PW qpJeKtH6VRnXfVFZwCZKCwHUxV/cZ2pPO4flE4Qql1RE7K2WX48GBk7fw2v38EqZGIRx uRXwnCGjK7SSRaxKl0/2qQ+E4vXawTrWYmb/dKVDzNrAA9CTFcixMEA2L/IMrVaebEg7 D3mVn95hMZcdkEETYr5mxJikmg+AT4NAxBAbVMyemW4m6Aa+ukKomM/n8GwzStyYJtcQ Rn/w== X-Gm-Message-State: AOAM5305NoOYhluwC6LJ46pLISdE5UsutCA7AbdhFQrapFNowJQKtnBh zbJVVa/7wyIWm2HBlRWubNo= X-Google-Smtp-Source: ABdhPJxymHiGb/iXo60o4r4ayfKgHxgUGULh6sa0J7CxWTontJBCxZlFSk8UEcZl0Ihhu+tDlai08w== X-Received: by 2002:a02:b60a:: with SMTP id h10mr1116894jam.99.1610483549482; Tue, 12 Jan 2021 12:32:29 -0800 (PST) Received: from ubuntu-m3-large-x86 ([2604:1380:45f1:1d00::1]) by smtp.gmail.com with ESMTPSA id v3sm3094783ilj.28.2021.01.12.12.32.28 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 12 Jan 2021 12:32:28 -0800 (PST) Date: Tue, 12 Jan 2021 13:32:26 -0700 From: Nathan Chancellor To: syzbot Cc: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com, clang-built-linux@googlegroups.com, Dmitry Vyukov , Marco Elver Subject: Re: upstream build error (12) Message-ID: <20210112203226.GA1055929@ubuntu-m3-large-x86> References: <0000000000004a33a005b8b8eaab@google.com> <20210112194058.GA200254@ubuntu-m3-large-x86> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210112194058.GA200254@ubuntu-m3-large-x86> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jan 12, 2021 at 12:40:58PM -0700, Nathan Chancellor wrote: > On Tue, Jan 12, 2021 at 11:20:27AM -0800, syzbot wrote: > > Hello, > > > > syzbot found the following issue on: > > > > HEAD commit: e609571b Merge tag 'nfs-for-5.11-2' of git://git.linux-nfs.. > > git tree: upstream > > console output: https://syzkaller.appspot.com/x/log.txt?x=15965a00d00000 > > kernel config: https://syzkaller.appspot.com/x/.config?x=6157970d0a91b812 > > dashboard link: https://syzkaller.appspot.com/bug?extid=76880518931d755473cf > > compiler: clang version 11.0.0 (https://github.com/llvm/llvm-project.git ca2dcbd030eadbf0aa9b660efe864ff08af6e18b) > > > > IMPORTANT: if you fix the issue, please add the following tag to the commit: > > Reported-by: syzbot+76880518931d755473cf@syzkaller.appspotmail.com > > > > clang-11: error: unable to execute command: Aborted (core dumped) > > clang-11: error: clang frontend command failed due to signal (use -v to see invocation) > > > > --- > > This report is generated by a bot. It may contain errors. > > See https://goo.gl/tpsmEJ for more information about syzbot. > > syzbot engineers can be reached at syzkaller@googlegroups.com. > > > > syzbot will keep track of this issue. See: > > https://goo.gl/tpsmEJ#status for how to communicate with syzbot. > > Would it be possible for clang-built-linux@googlegroups.com to be CC'd > when there is a build error and the compiler is clang? Especially if > clang is hitting an assertion. I cannot reproduce this with clang 11.0.1. I did a reverse bisect on LLVM and found commit 4b0aa5724fea ("Change the INLINEASM_BR MachineInstr to be a non-terminating instruction.") as the fix (which makes sense, that commit has direct kernel implications). It is probably worth upgrading syzkaller's clang to 11.0.1, where I have not seen any assertions across all of the configurations that I test. Ccing Dmitry and Marco directly. Cheers, Nathan