From: syzbot <syzbot+889cc963ed79ee90f74f@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, axboe@kernel.dk, hannes@cmpxchg.org,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
schatzberg.dan@gmail.com, sfr@canb.auug.org.au,
syzkaller-bugs@googlegroups.com
Subject: Re: general protection fault in __queue_work (2)
Date: Sat, 07 Mar 2020 09:55:02 -0800 [thread overview]
Message-ID: <000000000000252cf605a0477843@google.com> (raw)
In-Reply-To: <000000000000a98a1705a03bbcbe@google.com>
syzbot has bisected this bug to:
commit 29dab2122492f6dbc0b895ca5bd047e166684d1a
Author: Dan Schatzberg <schatzberg.dan@gmail.com>
Date: Tue Feb 25 04:14:07 2020 +0000
loop: use worker per cgroup instead of kworker
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14d6b01de00000
start commit: 770fbb32 Add linux-next specific files for 20200228
git tree: linux-next
final crash: https://syzkaller.appspot.com/x/report.txt?x=16d6b01de00000
console output: https://syzkaller.appspot.com/x/log.txt?x=12d6b01de00000
kernel config: https://syzkaller.appspot.com/x/.config?x=576314276bce4ad5
dashboard link: https://syzkaller.appspot.com/bug?extid=889cc963ed79ee90f74f
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=176d7f29e00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=134c481de00000
Reported-by: syzbot+889cc963ed79ee90f74f@syzkaller.appspotmail.com
Fixes: 29dab2122492 ("loop: use worker per cgroup instead of kworker")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2020-03-07 17:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-07 3:55 general protection fault in __queue_work (2) syzbot
2020-03-07 17:55 ` syzbot [this message]
[not found] <20200308094448.15320-1-hdanton@sina.com>
2020-03-08 16:17 ` Jens Axboe
[not found] ` <20200309020900.16756-1-hdanton@sina.com>
2020-03-09 2:17 ` Jens Axboe
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=000000000000252cf605a0477843@google.com \
--to=syzbot+889cc963ed79ee90f74f@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=hannes@cmpxchg.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=schatzberg.dan@gmail.com \
--cc=sfr@canb.auug.org.au \
--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).