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=-16.4 required=3.0 tests=BAYES_00,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 558FFC433E2 for ; Wed, 16 Sep 2020 05:49:51 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 029EF2076B for ; Wed, 16 Sep 2020 05:49:50 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=google.com header.i=@google.com header.b="sxdT1JFx" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726198AbgIPFts (ORCPT ); Wed, 16 Sep 2020 01:49:48 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36350 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726172AbgIPFtp (ORCPT ); Wed, 16 Sep 2020 01:49:45 -0400 Received: from mail-qt1-x842.google.com (mail-qt1-x842.google.com [IPv6:2607:f8b0:4864:20::842]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0FD49C06174A for ; Tue, 15 Sep 2020 22:49:43 -0700 (PDT) Received: by mail-qt1-x842.google.com with SMTP id y11so5257111qtn.9 for ; Tue, 15 Sep 2020 22:49:42 -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=lMGz7FPVGblmyw2B5oS0Nz9bMOQ+2e+FoQEBHmc88aM=; b=sxdT1JFxxNg0Rds661U0501ccGvxzKZZN08GzqkQ5Ytaa+KjkLkvhcXB2dybgG/+Wy GgX4GarkTHXMh2Ilmt4pwM1A8LP+Hoo8jFjWH9B7d+6QwIdP+0Y/7oCCEXGhWqXALQb1 TTbOHmCLsizcWv4lYVuKOYqQy+vZPVDti27lL54Nd3mx41bRnlpAW5bwXS8KosTGR8K0 Z72CrF1PkX9n4B7fuhh8YiQBHQBJak3/YgE1xRfQaKfMdMmetp3HRi/+evqTzI6gVxU3 YHCaCw3H8IkiDMEU8DMWU0CAN9pkBgOcZ/fLSEkxv520qk7XJJmelMAyLwA0V5RR2031 VGPw== 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=lMGz7FPVGblmyw2B5oS0Nz9bMOQ+2e+FoQEBHmc88aM=; b=Lf7NFK0U2H+mD8ShNQv4rXFhVje52vJtgVa/Vu30C6rz02tdV5X89YtoGQi7TKzjor Fu5bATy+icT4Y3X+h/LUS8vsq78lFfi5CQX5KPnarwe7MZSgVQgK8Uu6pOGH+SVyVZGt TJEZtcIrGRgglEi0EaVTrXVGlZHq0Or/SK75QSNuPSe0gXeipJVlCD9cv/7HMdBRbJ8g Q/7aZLlJc3UF+cHVEF3hYaarAdmLSdKiwQZdJrlMU455mJvrow1F2EntSQtUGhCYt427 XO1amHkkvhrXeT8tYiWLfRzyv5atP7Nbme2VfpYniqCGsd2M7MwXmEwTueOAEwBWeu9W VupA== X-Gm-Message-State: AOAM532j3YreK1L0qqmt9LwTKjahhp4thAth/4FoY0mzsnYU+p5+yuQB KT9nd9NCHDy1HNUutZRnZ9+VHMpAuMkWBQOrKJ76Dw== X-Google-Smtp-Source: ABdhPJyyHp9sBD6IlRiIYya/rM8aE29AYKNr2HPFScbwx+XNCVoWT69th17AbZXIfJrSf0zN4+tAFfdwmieMkd8iTQI= X-Received: by 2002:ac8:5215:: with SMTP id r21mr21225391qtn.257.1600235381845; Tue, 15 Sep 2020 22:49:41 -0700 (PDT) MIME-Version: 1.0 References: <00000000000059b6d40594d0f776@google.com> <7cff3e3e-4003-a2bc-9917-a006e76854c8@gmail.com> In-Reply-To: <7cff3e3e-4003-a2bc-9917-a006e76854c8@gmail.com> From: Dmitry Vyukov Date: Wed, 16 Sep 2020 07:49:30 +0200 Message-ID: Subject: Re: WARNING in batadv_iv_send_outstanding_bat_ogm_packet To: Anant Thazhemadam Cc: syzkaller-bugs , syzkaller , LKML 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 Wed, Sep 16, 2020 at 7:43 AM Anant Thazhemadam wrote: > > > On 16/09/20 10:25 am, Dmitry Vyukov wrote: > > On Tue, Sep 15, 2020 at 8:34 PM Anant Thazhemadam > > wrote: > >> On Monday, October 14, 2019 at 2:25:08 AM UTC+5:30 syzbot wrote: > >>> Hello, > >>> > >>> syzbot found the following crash on: > >>> > >>> HEAD commit: da940012 Merge tag 'char-misc-5.4-rc3' of git://git.kernel.. > >>> git tree: upstream > >>> console output: https://syzkaller.appspot.com/x/log.txt?x=13ffd808e00000 > >>> kernel config: https://syzkaller.appspot.com/x/.config?x=2d2fd92a28d3e50 > >>> dashboard link: https://syzkaller.appspot.com/bug?extid=c0b807de416427ff3dd1 > >>> compiler: clang version 9.0.0 (/home/glider/llvm/clang > >>> 80fee25776c2fb61e74c1ecb1a523375c2500b69) > >>> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=141ffd77600000 > >>> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11edd580e00000 > >>> > >>> IMPORTANT: if you fix the bug, please add the following tag to the commit: > >>> Reported-by: syzbot+c0b807...@syzkaller.appspotmail.com > >>> > >>> ------------[ cut here ]------------ > >>> WARNING: CPU: 1 PID: 30 at net/batman-adv/bat_iv_ogm.c:382 > >>> batadv_iv_ogm_emit net/batman-adv/bat_iv_ogm.c:382 [inline] > >>> WARNING: CPU: 1 PID: 30 at net/batman-adv/bat_iv_ogm.c:382 > >>> batadv_iv_send_outstanding_bat_ogm_packet+0x6b4/0x770 > >>> net/batman-adv/bat_iv_ogm.c:1663 > >>> Kernel panic - not syncing: panic_on_warn set ... > >>> CPU: 1 PID: 30 Comm: kworker/u4:2 Not tainted 5.4.0-rc2+ #0 > >>> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS > >>> Google 01/01/2011 > >>> Workqueue: bat_events batadv_iv_send_outstanding_bat_ogm_packet > >>> Call Trace: > >>> __dump_stack lib/dump_stack.c:77 [inline] > >>> dump_stack+0x1d8/0x2f8 lib/dump_stack.c:113 > >>> panic+0x264/0x7a9 kernel/panic.c:221 > >>> __warn+0x20e/0x210 kernel/panic.c:582 > >>> report_bug+0x1b6/0x2f0 lib/bug.c:195 > >>> fixup_bug arch/x86/kernel/traps.c:179 [inline] > >>> do_error_trap+0xd7/0x440 arch/x86/kernel/traps.c:272 > >>> do_invalid_op+0x36/0x40 arch/x86/kernel/traps.c:291 > >>> invalid_op+0x23/0x30 arch/x86/entry/entry_64.S:1028 > >>> RIP: 0010:batadv_iv_ogm_emit net/batman-adv/bat_iv_ogm.c:382 [inline] > >>> RIP: 0010:batadv_iv_send_outstanding_bat_ogm_packet+0x6b4/0x770 > >>> net/batman-adv/bat_iv_ogm.c:1663 > >>> Code: 66 05 00 eb 05 e8 9c 48 23 fa 48 83 c4 68 5b 41 5c 41 5d 41 5e 41 5f > >>> 5d c3 e8 88 48 23 fa 0f 0b e9 34 ff ff ff e8 7c 48 23 fa <0f> 0b e9 28 ff > >>> ff ff 89 d9 80 e1 07 80 c1 03 38 c1 0f 8c c1 f9 ff > >>> RSP: 0018:ffff8880a9abfc48 EFLAGS: 00010293 > >>> RAX: ffffffff874fe8a4 RBX: ffff888094160870 RCX: ffff8880a9ab2080 > >>> RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000002 > >>> RBP: ffff8880a9abfcd8 R08: ffffffff874fe28e R09: ffffed10123e6969 > >>> R10: ffffed10123e6969 R11: 0000000000000000 R12: ffff888091f34000 > >>> R13: dffffc0000000000 R14: ffff8880a80c5000 R15: ffff8880a4481400 > >>> process_one_work+0x7ef/0x10e0 kernel/workqueue.c:2269 > >>> worker_thread+0xc01/0x1630 kernel/workqueue.c:2415 > >>> kthread+0x332/0x350 kernel/kthread.c:255 > >>> ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:352 > >>> Kernel Offset: disabled > >>> Rebooting in 86400 seconds.. > >>> > >>> > >>> --- > >>> 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 syzk...@googlegroups.com. > >>> > >>> syzbot will keep track of this bug report. See: > >>> https://goo.gl/tpsmEJ#status for how to communicate with syzbot. > >>> syzbot can test patches for this bug, for details see: > >>> https://goo.gl/tpsmEJ#testing-patches > >> > >> For this bug, syzbot does not seem to be able to build the kernel anymore. > >> Can bugs like these be considered and closed as invalid? > >> > >> Thanks, > >> Anant > > Hi Anant, > > > > +syzkaler, lkml (nobody is generally reading syzkaller-bugs). > > > > What do you mean by "not able to build a kernel for this bug"? > > Building a kernel is not related to a particular bug. It's the same > > for all bugs... > > Hi, > > I thought this might be a query that's better suited for the syzkaller groups, > and hence posted it on there. > > I wanted to check if this bug was still present and relevant, so I tried to check > by sending a syz test request for the upstream kernel (the dashboard shows > that the error was found in the upstream kernel). > > However, I was notified later that the build/boot had failed. > Feel free to correct me if I'm wrong, but I doubt that the reason build/boot > had failed, was because of the bug itself (the error report is visible on the > bug's dashboard page itself). > > I wanted to know what was the typical protocol in cases like this. Would this be > a valid reason enough to close the bug as invalid? Or is there something else > that can be done, to indicate that the upstream kernel doesn't even build/boot > for this bug to be tested anymore? > If nothing else, how else can I try and get syzbot to test if this bug still exists or > not? > > Thanks, > Anant I see that config is not building anymore: BTF: .tmp_vmlinux.btf: pahole version v1.9 is too old, need at least v1.16 Failed to generate BTF for vmlinux Try to disable CONFIG_DEBUG_INFO_BTF Makefile:1162: recipe for target 'vmlinux' failed This is not anyhow top the bug itself, if it still happens or not. So this does not look like a valid reason to close the bug. There are two options: 1. Attach a patch for testing that disables CONFIG_DEBUG_INFO_BTF (e.g. delete it, or make it dependent on some disabled config, not sure what's the easiest working option). 2. Test locally with the config disabled.