From: syzbot <syzbot+fa64e680a1ff32087778@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, axboe@kernel.dk,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
pmladek@suse.com, qiang.zhang@windriver.com,
sfr@canb.auug.org.au, syzkaller-bugs@googlegroups.com
Subject: Re: WARNING in kthread_queue_work
Date: Wed, 15 Jul 2020 03:04:04 -0700 [thread overview]
Message-ID: <00000000000031a14405aa780bdb@google.com> (raw)
In-Reply-To: <000000000000e6807f05aa4608b7@google.com>
syzbot has bisected this issue to:
commit 4977caef05aa154f5e45a232fc4f0e1c74a0c739
Author: Zhang Qiang <qiang.zhang@windriver.com>
Date: Tue Jul 7 02:29:47 2020 +0000
kthread: work could not be queued when worker being destroyed
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12c58f57100000
start commit: 89032636 Add linux-next specific files for 20200708
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=11c58f57100000
console output: https://syzkaller.appspot.com/x/log.txt?x=16c58f57100000
kernel config: https://syzkaller.appspot.com/x/.config?x=64a250ebabc6c320
dashboard link: https://syzkaller.appspot.com/bug?extid=fa64e680a1ff32087778
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16bf9f2f100000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=118380ed100000
Reported-by: syzbot+fa64e680a1ff32087778@syzkaller.appspotmail.com
Fixes: 4977caef05aa ("kthread: work could not be queued when worker being destroyed")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2020-07-15 10:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-12 22:24 WARNING in kthread_queue_work syzbot
2020-07-15 10:04 ` syzbot [this message]
2020-07-15 11:15 ` Stephen Rothwell
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=00000000000031a14405aa780bdb@google.com \
--to=syzbot+fa64e680a1ff32087778@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=qiang.zhang@windriver.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 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.