From: syzbot <syzbot+bdcf141f362ef83335cf@syzkaller.appspotmail.com>
To: ast@kernel.org, bpf@vger.kernel.org, daniel@iogearbox.net,
davem@davemloft.net, edumazet@google.com, hdanton@sina.com,
jhs@mojatatu.com, jiri@resnulli.us, kuba@kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com, syzkaller-bugs@googlegroups.com,
xiyou.wangcong@gmail.com
Subject: Re: [syzbot] [net?] WARNING: ODEBUG bug in ingress_destroy
Date: Sat, 22 Jul 2023 00:38:23 -0700 [thread overview]
Message-ID: <00000000000057611806010e77fa@google.com> (raw)
In-Reply-To: <0000000000004386940600eca80d@google.com>
syzbot has bisected this issue to:
commit e420bed025071a623d2720a92bc2245c84757ecb
Author: Daniel Borkmann <daniel@iogearbox.net>
Date: Wed Jul 19 14:08:52 2023 +0000
bpf: Add fd-based tcx multi-prog infra with link support
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1568abf4a80000
start commit: 03b123debcbc tcp: tcp_enter_quickack_mode() should be static
git tree: net-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=1768abf4a80000
console output: https://syzkaller.appspot.com/x/log.txt?x=1368abf4a80000
kernel config: https://syzkaller.appspot.com/x/.config?x=32e3dcc11fd0d297
dashboard link: https://syzkaller.appspot.com/bug?extid=bdcf141f362ef83335cf
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10bf2bf4a80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12741e9aa80000
Reported-by: syzbot+bdcf141f362ef83335cf@syzkaller.appspotmail.com
Fixes: e420bed02507 ("bpf: Add fd-based tcx multi-prog infra with link support")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-07-22 7:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 15:18 [syzbot] [net?] WARNING: ODEBUG bug in ingress_destroy syzbot
2023-07-21 0:53 ` Daniel Borkmann
2023-07-22 7:38 ` syzbot [this message]
[not found] <20230721142839.388-1-hdanton@sina.com>
2023-07-22 0:54 ` syzbot
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=00000000000057611806010e77fa@google.com \
--to=syzbot+bdcf141f362ef83335cf@syzkaller.appspotmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hdanton@sina.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=xiyou.wangcong@gmail.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.