From: syzbot <syzbot+5609d37b3a926aad75b7@syzkaller.appspotmail.com>
To: ast@kernel.org, daniel@iogearbox.net,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: bpf-next test error: BUG: program execution failed: executor 0: exit status 67
Date: Thu, 15 Oct 2020 10:41:25 -0700 [thread overview]
Message-ID: <000000000000376ecf05b1b92848@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: e688c3db bpf: Fix register equivalence tracking.
git tree: bpf-next
console output: https://syzkaller.appspot.com/x/log.txt?x=13d3c678500000
kernel config: https://syzkaller.appspot.com/x/.config?x=ea7dc57e899da16d
dashboard link: https://syzkaller.appspot.com/bug?extid=5609d37b3a926aad75b7
compiler: gcc (GCC) 10.1.0-syz 20200507
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+5609d37b3a926aad75b7@syzkaller.appspotmail.com
executing program
2020/10/15 14:32:51 BUG: program execution failed: executor 0: exit status 67
iptable checkpoint filter/2: getsockopt(IPT_SO_GET_INFO) (errno 22)
loop exited with status 67
iptable checkpoint filter/2: getsockopt(IPT_SO_GET_INFO) (errno 22)
loop exited with status 67
---
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.
next reply other threads:[~2020-10-15 17:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 17:41 syzbot [this message]
2020-10-15 17:46 ` bpf-next test error: BUG: program execution failed: executor 0: exit status 67 Dmitry Vyukov
2020-10-15 18:02 ` Jakub Kicinski
2020-10-15 18:04 ` Jakub Kicinski
2020-10-16 10:04 ` Dmitry Vyukov
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=000000000000376ecf05b1b92848@google.com \
--to=syzbot+5609d37b3a926aad75b7@syzkaller.appspotmail.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.