On Thu, Oct 15, 2020 at 8:04 PM Jakub Kicinski <kuba@xxxxxxxxxx> wrote: > > > <syzbot+5609d37b3a926aad75b7@xxxxxxxxxxxxxxxxxxxxxxxxx> 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@xxxxxxxxxxxxxxxxxxxxxxxxx > > > > > > > > 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") > > Ah, you're saying it's just linux-next and bpf-next that's down. > I think the quoted fix will hit bpf-next in a few hours. > > Thanks! Yes, stopped happening. Phew! #syz fix: netfilter: restore NF_INET_NUMHOOKS
