From: syzbot <syzbot+ba4bcf1563f90386910f@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: KASAN: use-after-free Write in tcindex_change
Date: Fri, 17 Apr 2020 12:05:02 -0700 [thread overview]
Message-ID: <00000000000000c55c05a3813a66@google.com> (raw)
In-Reply-To: <00000000000088487805a116880c@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=15a956d7e00000
start commit: ac309e77 Merge branch 'for-linus' of git://git.kernel.org/..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=6dfa02302d6db985
dashboard link: https://syzkaller.appspot.com/bug?extid=ba4bcf1563f90386910f
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1771b973e00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1248a61de00000
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-17 19:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-18 0:57 KASAN: use-after-free Write in tcindex_change syzbot
2020-03-18 1:59 ` syzbot
2020-04-17 19:05 ` syzbot [this message]
2020-11-11 13:11 ` 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=00000000000000c55c05a3813a66@google.com \
--to=syzbot+ba4bcf1563f90386910f@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 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.