From: Dmitry Vyukov <dvyukov@google.com>
To: syzbot <syzbot+c89a581922d5a98fccb8@syzkaller.appspotmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
netdev <netdev@vger.kernel.org>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>
Subject: Re: bpf build error (2)
Date: Thu, 28 Nov 2019 09:37:20 +0100 [thread overview]
Message-ID: <CACT4Y+YnLC93dzGE51KQmqwgOgcULtnE1fS_ruJns_Ar1uqYhg@mail.gmail.com> (raw)
In-Reply-To: <000000000000a54cd9059863fd8c@google.com>
On Thu, Nov 28, 2019 at 9:35 AM syzbot
<syzbot+c89a581922d5a98fccb8@syzkaller.appspotmail.com> 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
prev parent reply other threads:[~2019-11-28 8:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-28 8:35 bpf build error (2) syzbot
2019-11-28 8:37 ` Dmitry Vyukov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CACT4Y+YnLC93dzGE51KQmqwgOgcULtnE1fS_ruJns_Ar1uqYhg@mail.gmail.com \
--to=dvyukov@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzbot+c89a581922d5a98fccb8@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).