From: syzbot <syzbot+9880e421ec82313d6527@syzkaller.appspotmail.com>
To: amitoj1606@gmail.com, ap420073@gmail.com, avagin@gmail.com,
dbueso@suse.de, ebiederm@xmission.com,
jacek.anaszewski@gmail.com, linux-kernel@vger.kernel.org,
linux-leds@vger.kernel.org, linux-mm@kvack.org, oleg@redhat.com,
pavel@ucw.cz, prsood@codeaurora.org, rpurdie@rpsys.net,
syzkaller-bugs@googlegroups.com, tj@kernel.org
Subject: Re: INFO: task hung in do_exit
Date: Sat, 13 Apr 2019 19:55:00 -0700 [thread overview]
Message-ID: <00000000000074e9d5058674a94f@google.com> (raw)
In-Reply-To: <000000000000e02bf505866414ae@google.com>
syzbot has bisected this bug to:
commit 430e48ecf31f4f897047f22e02abdfa75730cad8
Author: Amitoj Kaur Chawla <amitoj1606@gmail.com>
Date: Thu Aug 10 16:28:09 2017 +0000
leds: lm3533: constify attribute_group structure
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15f4cee3200000
start commit: 8ee15f32 Merge tag 'dma-mapping-5.1-1' of git://git.infrad..
git tree: upstream
final crash: https://syzkaller.appspot.com/x/report.txt?x=17f4cee3200000
console output: https://syzkaller.appspot.com/x/log.txt?x=13f4cee3200000
kernel config: https://syzkaller.appspot.com/x/.config?x=4fb64439e07a1ec0
dashboard link: https://syzkaller.appspot.com/bug?extid=9880e421ec82313d6527
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=149b89af200000
Reported-by: syzbot+9880e421ec82313d6527@syzkaller.appspotmail.com
Fixes: 430e48ecf31f ("leds: lm3533: constify attribute_group structure")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next parent reply other threads:[~2019-04-14 2:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000000000000e02bf505866414ae@google.com>
2019-04-14 2:55 ` syzbot [this message]
2019-04-14 7:59 ` INFO: task hung in do_exit Pavel Machek
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=00000000000074e9d5058674a94f@google.com \
--to=syzbot+9880e421ec82313d6527@syzkaller.appspotmail.com \
--cc=amitoj1606@gmail.com \
--cc=ap420073@gmail.com \
--cc=avagin@gmail.com \
--cc=dbueso@suse.de \
--cc=ebiederm@xmission.com \
--cc=jacek.anaszewski@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=oleg@redhat.com \
--cc=pavel@ucw.cz \
--cc=prsood@codeaurora.org \
--cc=rpurdie@rpsys.net \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tj@kernel.org \
/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).