From: Dmitry Vyukov <dvyukov@google.com>
To: syzbot <syzbot+ba4bcf1563f90386910f@syzkaller.appspotmail.com>,
LKML <linux-kernel@vger.kernel.org>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
netdev <netdev@vger.kernel.org>
Subject: Re: KASAN: use-after-free Write in tcindex_change
Date: Wed, 11 Nov 2020 14:11:47 +0100 [thread overview]
Message-ID: <CACT4Y+a0QfyMHLv0RP-=ihAUNpJpAVJbHFUWa6RT_0RupBE31g@mail.gmail.com> (raw)
In-Reply-To: <00000000000000c55c05a3813a66@google.com>
On Fri, Apr 17, 2020 at 9:05 PM syzbot
<syzbot+ba4bcf1563f90386910f@syzkaller.appspotmail.com> wrote:
>
> 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
#syz fix: net_sched: keep alloc_hash updated after hash allocation
prev parent reply other threads:[~2020-11-11 13:12 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
2020-11-11 13:11 ` Dmitry Vyukov [this message]
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='CACT4Y+a0QfyMHLv0RP-=ihAUNpJpAVJbHFUWa6RT_0RupBE31g@mail.gmail.com' \
--to=dvyukov@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzbot+ba4bcf1563f90386910f@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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).