From: syzbot <syzbot+92a80fff3b3af6c4464e@syzkaller.appspotmail.com>
To: davem@davemloft.net, 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: general protection fault in tcf_action_destroy (2)
Date: Tue, 28 Apr 2020 20:03:03 -0700 [thread overview]
Message-ID: <000000000000c3b0f205a4652f38@google.com> (raw)
In-Reply-To: <0000000000006601b005a08774fd@google.com>
syzbot suspects this bug was fixed by commit:
commit 0d1c3530e1bd38382edef72591b78e877e0edcd3
Author: Cong Wang <xiyou.wangcong@gmail.com>
Date: Thu Mar 12 05:42:28 2020 +0000
net_sched: keep alloc_hash updated after hash allocation
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15e74154100000
start commit: 67d584e3 Merge tag 'for-5.6-rc6-tag' of git://git.kernel.o..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=9f894bd92023de02
dashboard link: https://syzkaller.appspot.com/bug?extid=92a80fff3b3af6c4464e
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=160c3223e00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14f790ade00000
If the result looks correct, please mark the bug fixed by replying with:
#syz fix: net_sched: keep alloc_hash updated after hash allocation
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2020-04-29 3:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-10 22:15 general protection fault in tcf_action_destroy (2) syzbot
2020-03-10 22:48 ` syzbot
2020-04-29 3:03 ` syzbot [this message]
2020-11-11 13:13 ` 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=000000000000c3b0f205a4652f38@google.com \
--to=syzbot+92a80fff3b3af6c4464e@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--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).