From: Vinod Koul <vkoul@kernel.org>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Cc: syzbot <syzbot+6593c6b8c8b66a07cd98@syzkaller.appspotmail.com>,
alsa-devel@alsa-project.org, bp@alien8.de,
gregkh@linuxfoundation.org, hpa@zytor.com,
linux-kernel@vger.kernel.org, mingo@redhat.com, nstange@suse.de,
pierre-louis.bossart@linux.intel.com, sanyog.r.kale@intel.com,
syzkaller-bugs@googlegroups.com, tglx@linutronix.de,
x86@kernel.org, yakui.zhao@intel.com
Subject: Re: INFO: rcu detected stall in __do_softirq
Date: Sat, 17 Aug 2019 12:44:40 +0530 [thread overview]
Message-ID: <20190817071440.GD12733@vkoul-mobl.Dlink> (raw)
In-Reply-To: <63c0dc1e-323d-d46e-2d4a-b5b6d6916042@linaro.org>
On 16-08-19, 09:55, Srinivas Kandagatla wrote:
>
>
> On 16/08/2019 01:10, syzbot wrote:
> > syzbot has bisected this bug to:
> >
> > commit 2aeac95d1a4cc85aae57ab842d5c3340df0f817f
> > Author: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
> > Date: Tue Jun 11 10:40:41 2019 +0000
> >
> > soundwire: add module_sdw_driver helper macro
>
> Not sure how adding a macro with no users triggers this rcu stall.
And config used doesn't have soundwire set :D
>
> BTW this was in mainline since rc1.
This is caused by something else!
>
> --srini
>
> >
> > bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=114b45ee600000
> > start commit: 882e8691 Add linux-next specific files for 20190801
> > git tree: linux-next
> > final crash: https://syzkaller.appspot.com/x/report.txt?x=134b45ee600000
> > console output: https://syzkaller.appspot.com/x/log.txt?x=154b45ee600000
> > kernel config: https://syzkaller.appspot.com/x/.config?x=466b331af3f34e94
> > dashboard link:
> > https://syzkaller.appspot.com/bug?extid=6593c6b8c8b66a07cd98
> > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16b216b2600000
> >
> > Reported-by: syzbot+6593c6b8c8b66a07cd98@syzkaller.appspotmail.com
> > Fixes: 2aeac95d1a4c ("soundwire: add module_sdw_driver helper macro")
> >
> > For information about bisection process see:
> > https://goo.gl/tpsmEJ#bisection
--
~Vinod
prev parent reply other threads:[~2019-08-17 7:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-05 15:28 INFO: rcu detected stall in __do_softirq syzbot
2019-08-16 0:10 ` syzbot
2019-08-16 8:55 ` Srinivas Kandagatla
2019-08-17 7:14 ` Vinod Koul [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=20190817071440.GD12733@vkoul-mobl.Dlink \
--to=vkoul@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=bp@alien8.de \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=nstange@suse.de \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=sanyog.r.kale@intel.com \
--cc=srinivas.kandagatla@linaro.org \
--cc=syzbot+6593c6b8c8b66a07cd98@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yakui.zhao@intel.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.