From: Jakub Kicinski <kuba@kernel.org>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: syzbot <syzbot+5609d37b3a926aad75b7@syzkaller.appspotmail.com>,
NetFilter <netfilter-devel@vger.kernel.org>,
Pablo Neira Ayuso <pablo@netfilter.org>,
syzkaller <syzkaller@googlegroups.com>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
LKML <linux-kernel@vger.kernel.org>,
netdev <netdev@vger.kernel.org>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>
Subject: Re: bpf-next test error: BUG: program execution failed: executor 0: exit status 67
Date: Thu, 15 Oct 2020 11:02:08 -0700 [thread overview]
Message-ID: <20201015110203.7cffc1d4@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> (raw)
In-Reply-To: <CACT4Y+aTPCPRtJ2wJ5P58DijtG2pxXtZm6w=C838YKLKCEdSfw@mail.gmail.com>
On Thu, 15 Oct 2020 19:46:35 +0200 Dmitry Vyukov wrote:
> On Thu, Oct 15, 2020 at 7:41 PM syzbot
> <syzbot+5609d37b3a926aad75b7@syzkaller.appspotmail.com> wrote:
> >
> > 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
>
> +netfilter maintainers
>
> It seems one of these recent commits broke netfiler.
> Since syzkaller uses netfiler for sandboxing, syzbot is currently down
> on bpf-next and linux-next. Other trees will follow once they merge
> the breakage.
Do you have this?
d25e2e9388ed ("netfilter: restore NF_INET_NUMHOOKS")
next prev parent reply other threads:[~2020-10-15 18:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 17:41 bpf-next test error: BUG: program execution failed: executor 0: exit status 67 syzbot
2020-10-15 17:46 ` Dmitry Vyukov
2020-10-15 18:02 ` Jakub Kicinski [this message]
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=20201015110203.7cffc1d4@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com \
--to=kuba@kernel.org \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=dvyukov@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=syzbot+5609d37b3a926aad75b7@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=syzkaller@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.