From: syzbot <syzbot+1c9db6a163a4000d0765@syzkaller.appspotmail.com>
To: asmadeus@codewreck.org, davem@davemloft.net,
dominique.martinet@cea.fr, ericvh@gmail.com,
jiangyiwen@huwei.com, linux-kernel@vger.kernel.org,
lucho@ionkov.net, netdev@vger.kernel.org, rminnich@sandia.gov,
syzkaller-bugs@googlegroups.com, tomasbortoli@gmail.com,
v9fs-developer@lists.sourceforge.net, viro@zeniv.linux.org.uk
Subject: Re: KASAN: use-after-free Read in __queue_work (2)
Date: Sat, 07 Dec 2019 11:45:00 -0800 [thread overview]
Message-ID: <000000000000de09e70599226583@google.com> (raw)
In-Reply-To: <000000000000f665a30570885589@google.com>
syzbot suspects this bug was fixed by commit:
commit 430ac66eb4c5b5c4eb846b78ebf65747510b30f1
Author: Tomas Bortoli <tomasbortoli@gmail.com>
Date: Fri Jul 20 09:27:30 2018 +0000
net/9p/trans_fd.c: fix race-condition by flushing workqueue before the
kfree()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15661282e00000
start commit: ca04b3cc Merge tag 'armsoc-fixes' of git://git.kernel.org/..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=2ca6c7a31d407f86
dashboard link: https://syzkaller.appspot.com/bug?extid=1c9db6a163a4000d0765
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1473a452400000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14087748400000
If the result looks correct, please mark the bug fixed by replying with:
#syz fix: net/9p/trans_fd.c: fix race-condition by flushing workqueue
before the kfree()
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2019-12-07 19:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-09 3:09 KASAN: use-after-free Read in __queue_work (2) syzbot
2019-11-23 23:37 ` syzbot
2019-12-07 19:45 ` syzbot [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=000000000000de09e70599226583@google.com \
--to=syzbot+1c9db6a163a4000d0765@syzkaller.appspotmail.com \
--cc=asmadeus@codewreck.org \
--cc=davem@davemloft.net \
--cc=dominique.martinet@cea.fr \
--cc=ericvh@gmail.com \
--cc=jiangyiwen@huwei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lucho@ionkov.net \
--cc=netdev@vger.kernel.org \
--cc=rminnich@sandia.gov \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tomasbortoli@gmail.com \
--cc=v9fs-developer@lists.sourceforge.net \
--cc=viro@zeniv.linux.org.uk \
/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.