From: syzbot <syzbot+5f66662adc70969940fd@syzkaller.appspotmail.com>
To: davem@davemloft.net, hdanton@sina.com, jhs@mojatatu.com,
jiri@resnulli.us, kuba@kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com,
xiyou.wangcong@gmail.com
Subject: Re: BUG: unable to handle kernel paging request in tcf_action_dump_terse
Date: Mon, 05 Oct 2020 01:10:05 -0700 [thread overview]
Message-ID: <00000000000094e3c805b0e802a8@google.com> (raw)
In-Reply-To: <000000000000b3d57105b05ab856@google.com>
syzbot has bisected this issue to:
commit 0fedc63fadf0404a729e73a35349481c8009c02f
Author: Cong Wang <xiyou.wangcong@gmail.com>
Date: Wed Sep 23 03:56:24 2020 +0000
net_sched: commit action insertions together
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12c20657900000
start commit: 2172e358 Add linux-next specific files for 20201002
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=11c20657900000
console output: https://syzkaller.appspot.com/x/log.txt?x=16c20657900000
kernel config: https://syzkaller.appspot.com/x/.config?x=70698f530a7e856f
dashboard link: https://syzkaller.appspot.com/bug?extid=5f66662adc70969940fd
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=142fd4af900000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16ffcdeb900000
Reported-by: syzbot+5f66662adc70969940fd@syzkaller.appspotmail.com
Fixes: 0fedc63fadf0 ("net_sched: commit action insertions together")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2020-10-05 8:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-28 7:36 BUG: unable to handle kernel paging request in tcf_action_dump_terse syzbot
2020-10-04 8:48 ` syzbot
2020-10-05 8:10 ` syzbot [this message]
2020-10-11 19:15 ` Cong Wang
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=00000000000094e3c805b0e802a8@google.com \
--to=syzbot+5f66662adc70969940fd@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).