Re: bpf-next test error: BUG: program execution failed: executor 0: exit status 67

Re: bpf-next test error: BUG: program execution failed: executor 0: exit status 67

[Dmitry Vyukov]

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.

$ git log --format="%h %cd %s"  net/netfilter/ller
d483842df20a7 Thu Oct 15 13:12:59 2020 +1100 Merge remote-tracking
branch 'net-next/master' into master
a307b1b214d05 Thu Oct 15 09:21:35 2020 +1100 Merge remote-tracking
branch 'wireless-drivers/master' into master
0d9826bc18ce3 Wed Oct 14 01:25:14 2020 +0200 netfilter: nf_log:
missing vlan offload tag and proto
98a381a7d4892 Mon Oct 12 16:54:30 2020 +0200 netfilter: nftables:
extend error reporting for chain updates
7980d2eabde82 Mon Oct 12 01:59:41 2020 +0200 ipvs: clear skb->tstamp
in forwarding path
793d5d6124269 Mon Oct 12 01:58:10 2020 +0200 netfilter: flowtable:
reduce calls to pskb_may_pull()
d3519cb89f6d5 Mon Oct 12 01:57:34 2020 +0200 netfilter: nf_tables: add
inet ingress support
60a3815da702f Mon Oct 12 01:57:34 2020 +0200 netfilter: add inet ingress support
ddcfa710d40b3 Mon Oct 12 01:57:34 2020 +0200 netfilter: add
nf_ingress_hook() helper function
afd9024cd1fcf Mon Oct 12 01:57:34 2020 +0200 netfilter: add
nf_static_key_{inc,dec}
073b04e76be6d Mon Oct 12 01:57:34 2020 +0200 ipvs: inspect reply
packets from DR/TUN real servers
321e921daa05d Sun Oct 4 14:35:53 2020 -0700 Merge
git://git.kernel.org/pub/scm/linux/kernel/git/pablo/nf-next
10fdd6d80e4c2 Sun Oct 4 21:08:33 2020 +0200 netfilter: nf_tables:
Implement fast bitwise expression
5f48846daf332 Sun Oct 4 21:08:32 2020 +0200 netfilter: nf_tables:
Enable fast nft_cmp for inverted matches
ab6c41eefd46b Sun Oct 4 21:08:32 2020 +0200 netfilter: nfnetlink:
place subsys mutexes in distinct lockdep classes
9446ab34ace25 Sun Oct 4 21:08:25 2020 +0200 netfilter: ipset: enable
memory accounting for ipset allocations
82ec6630f9fcd Sun Oct 4 21:07:55 2020 +0200 netfilter:
nf_tables_offload: Remove unused macro FLOW_SETUP_BLOCK
66a9b9287d244 Fri Oct 2 19:11:11 2020 -0700 genetlink: move to smaller
ops wherever possible




> ---
> 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.
>
> --
> You received this message because you are subscribed to the Google Groups "syzkaller-bugs" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-bugs+unsubscribe@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/syzkaller-bugs/000000000000376ecf05b1b92848%40google.com.

Re: bpf-next test error: BUG: program execution failed: executor 0: exit status 67

[Jakub Kicinski]

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")

Re: bpf-next test error: BUG: program execution failed: executor 0: exit status 67

[Jakub Kicinski]

On Thu, 15 Oct 2020 11:02:08 -0700 Jakub Kicinski wrote:
> 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")

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!

Re: bpf-next test error: BUG: program execution failed: executor 0: exit status 67

[Dmitry Vyukov]

On Thu, Oct 15, 2020 at 8:04 PM Jakub Kicinski <kuba@kernel.org> wrote:
> > > <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")
>
> 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