From: syzbot <syzbot+d958a65633ea70280b23@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, axboe@kernel.dk,
dan.j.williams@intel.com, dhowells@redhat.com,
dvyukov@google.com, gregkh@linuxfoundation.org,
hannes@cmpxchg.org, joel@joelfernandes.org,
linux-block@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, mchehab+samsung@kernel.org,
mingo@redhat.com, patrick.bellasi@arm.com, rgb@redhat.com,
rostedt@goodmis.org, syzkaller-bugs@googlegroups.com,
viro@zeniv.linux.org.uk, yamada.masahiro@socionext.com
Subject: Re: KASAN: null-ptr-deref Write in io_wq_cancel_all
Date: Sat, 26 Oct 2019 23:33:00 -0700 [thread overview]
Message-ID: <000000000000fa2e630595de8d05@google.com> (raw)
In-Reply-To: <000000000000fbbe1e0595bac322@google.com>
syzbot has bisected this bug to:
commit d5f773aba1186142d52aef8242a426310a39fa86
Author: Jens Axboe <axboe@kernel.dk>
Date: Thu Oct 24 13:25:42 2019 +0000
io_uring: replace workqueue usage with io-wq
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=142c6d18e00000
start commit: 139c2d13 Add linux-next specific files for 20191025
git tree: linux-next
final crash: https://syzkaller.appspot.com/x/report.txt?x=162c6d18e00000
console output: https://syzkaller.appspot.com/x/log.txt?x=122c6d18e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=28fd7a693df38d29
dashboard link: https://syzkaller.appspot.com/bug?extid=d958a65633ea70280b23
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=160573c0e00000
Reported-by: syzbot+d958a65633ea70280b23@syzkaller.appspotmail.com
Fixes: d5f773aba118 ("io_uring: replace workqueue usage with io-wq")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
parent reply other threads:[~2019-10-27 6:33 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <000000000000fbbe1e0595bac322@google.com>]
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=000000000000fa2e630595de8d05@google.com \
--to=syzbot+d958a65633ea70280b23@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=dan.j.williams@intel.com \
--cc=dhowells@redhat.com \
--cc=dvyukov@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=hannes@cmpxchg.org \
--cc=joel@joelfernandes.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+samsung@kernel.org \
--cc=mingo@redhat.com \
--cc=patrick.bellasi@arm.com \
--cc=rgb@redhat.com \
--cc=rostedt@goodmis.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
--cc=yamada.masahiro@socionext.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).