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=-13.3 required=3.0 tests=DKIMWL_WL_MED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, MENTIONS_GIT_HOSTING,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,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 2F0BEC432C0 for ; Thu, 28 Nov 2019 08:37:35 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id ED8972158A for ; Thu, 28 Nov 2019 08:37:34 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=google.com header.i=@google.com header.b="QZshRNUZ" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727239AbfK1Ihe (ORCPT ); Thu, 28 Nov 2019 03:37:34 -0500 Received: from mail-qt1-f194.google.com ([209.85.160.194]:44082 "EHLO mail-qt1-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726558AbfK1Ihd (ORCPT ); Thu, 28 Nov 2019 03:37:33 -0500 Received: by mail-qt1-f194.google.com with SMTP id g24so21493521qtq.11 for ; Thu, 28 Nov 2019 00:37:33 -0800 (PST) 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=6u7P0pT+m1avw2GIFNYZQ34T01piQ8kE385X/AIq78g=; b=QZshRNUZBr5ALtvOYHI55X9QPZjYHWQM6OkQ26CESw8JOkaLWVE3SCNpz6Jxef3GK1 N63xpQJB3YzktG8IgnD8WPkjs25k2zaLapcvRmNuhJqR+zsJ96rCzPCwuc+NUs2VKMsS IPdzCRFYHKAkEPnN3iHHQGRzxdSa7BLD+dlI1rg7zgU32P2FLZGBiw8qabG37KMZBBhq m/BQiQ2m2RizbI01ONfvloWjp36yG7R/Y5ipDkoCyZ5gaszGdxvdIztLdI+lUtVWO9IY Dv7PKe/bGPx/jZvoGttLbsZWHGkox1cf1O6ebXIgh0rVbnWSzJRg1FHATqzYfx4o5zOV YWOQ== 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=6u7P0pT+m1avw2GIFNYZQ34T01piQ8kE385X/AIq78g=; b=sqjEZ9Kd1QwF0UIHjWNXDrrOj2Tk5/T1vndrnEvJhW1Y8jdtq54f7su4YjzCK7zEQJ eDl+GXX83z/ZpJFXvjc9YRMm1EmLmEJcJWHarA9G6l6YQ70x97JzH/rue1nHx/Jhxv/C gqTtwaDC2xXNsSRi42tmqipxP0okwyyb+OfBvI3ZHSHTYMiBEkmOBMi8FKjfyerLVuRN M7YQg2h8jl6Mz1R21bzBRH0+YLNhAz9Ho6dnelTGpyHQYLXRvWWqAktv2/3hzJlzDCij X9CxcUwIaeNcvxl6ujeKp4u6u4HV63vBK3nKjpSn1lehZchs4bjcetPgz1PCfwC2V0bz JlKw== X-Gm-Message-State: APjAAAWTl/bYHkvcKLReRTJG2Nn6FMe3XtttKBs5pD/S1Lattp+ogy3U HWQWsXQnbo8HlBf7APhtD2+1ro3pDcmdlZs+IKgngGgpfwE= X-Google-Smtp-Source: APXvYqy2wNwhnjUiRqGpMgfQGEjumGsSuvzRRhYXY9a/aMTl2PaNqNDT9FcS/UKU7vz5kiAskbxayH5YmZbjcEwXchY= X-Received: by 2002:ac8:6a0e:: with SMTP id t14mr10980160qtr.57.1574930252182; Thu, 28 Nov 2019 00:37:32 -0800 (PST) MIME-Version: 1.0 References: <000000000000a54cd9059863fd8c@google.com> In-Reply-To: <000000000000a54cd9059863fd8c@google.com> From: Dmitry Vyukov Date: Thu, 28 Nov 2019 09:37:20 +0100 Message-ID: Subject: Re: bpf build error (2) To: syzbot Cc: LKML , netdev , syzkaller-bugs Content-Type: text/plain; charset="UTF-8" Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org On Thu, Nov 28, 2019 at 9:35 AM syzbot wrote: > > Hello, > > syzbot found the following crash on: > > HEAD commit: 7c3977d1 libbpf: Fix sym->st_value print on 32-bit arches > git tree: bpf > console output: https://syzkaller.appspot.com/x/log.txt?x=108ab832e00000 > kernel config: https://syzkaller.appspot.com/x/.config?x=7a7e892e3a014d76 > dashboard link: https://syzkaller.appspot.com/bug?extid=c89a581922d5a98fccb8 > compiler: gcc (GCC) 9.0.0 20181231 (experimental) > > Unfortunately, I don't have any reproducer for this crash yet. > > IMPORTANT: if you fix the bug, please add the following tag to the commit: > Reported-by: syzbot+c89a581922d5a98fccb8@syzkaller.appspotmail.com > > failed to run ["make" "bzImage" "CC=/syzkaller/gcc/bin/gcc" "-j64"]: exit > status 2 > > --- > This bug 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 bug report. See: > https://goo.gl/tpsmEJ#status for how to communicate with syzbot. syzbot distro does not provide pahole 1.13, so I followed the suggestion and disabled CONFIG_DEBUG_INFO_BTF: https://github.com/google/syzkaller/commit/861a5980df642d6b9fb59fda98d5a75a019f5f34 #syz invalid