From: syzbot <syzbot+69904c3b4a09e8fa2e1b@syzkaller.appspotmail.com>
To: a@unstable.cc, alsa-devel@alsa-project.org,
b.a.t.m.a.n@lists.open-mesh.org, broonie@kernel.org,
davem@davemloft.net, dvyukov@google.com, edumazet@google.com,
hdanton@sina.com, jhs@mojatatu.com, jiri@resnulli.us,
kuba@kernel.org, lgirdwood@gmail.com,
linux-kernel@vger.kernel.org, mareklindner@neomailbox.ch,
netdev@vger.kernel.org, pabeni@redhat.com, perex@perex.cz,
povik+lin@cutebit.org, steve@sk2.org, sven@narfation.org,
sw@simonwunderlich.de, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de, tiwai@suse.com,
tonymarislogistics@yandex.com, xiyou.wangcong@gmail.com
Subject: Re: [syzbot] INFO: rcu detected stall in batadv_nc_worker (3)
Date: Sun, 16 Oct 2022 10:34:23 -0700 [thread overview]
Message-ID: <00000000000013612005eb2a4525@google.com> (raw)
In-Reply-To: <0000000000009d327505b0999237@google.com>
syzbot has bisected this issue to:
commit f8a4018c826fde6137425bbdbe524d5973feb173
Author: Mark Brown <broonie@kernel.org>
Date: Thu Jun 2 13:53:04 2022 +0000
ASoC: tas2770: Use modern ASoC DAI format terminology
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=164d4978880000
start commit: 55be6084c8e0 Merge tag 'timers-core-2022-10-05' of git://g..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=154d4978880000
console output: https://syzkaller.appspot.com/x/log.txt?x=114d4978880000
kernel config: https://syzkaller.appspot.com/x/.config?x=df75278aabf0681a
dashboard link: https://syzkaller.appspot.com/bug?extid=69904c3b4a09e8fa2e1b
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16e2e478880000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=149ca17c880000
Reported-by: syzbot+69904c3b4a09e8fa2e1b@syzkaller.appspotmail.com
Fixes: f8a4018c826f ("ASoC: tas2770: Use modern ASoC DAI format terminology")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2022-10-16 17:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-01 10:35 INFO: rcu detected stall in batadv_nc_worker (3) syzbot
2020-10-01 10:46 ` Dmitry Vyukov
2022-10-15 19:01 ` [syzbot] " syzbot
2022-10-16 17:34 ` syzbot [this message]
[not found] <20221015234821.438-1-hdanton@sina.com>
2022-10-16 0:13 ` syzbot
[not found] <20221016014012.519-1-hdanton@sina.com>
2022-10-16 3:03 ` syzbot
[not found] <20221016044826.637-1-hdanton@sina.com>
2022-10-16 12:27 ` syzbot
[not found] <20221016110248.708-1-hdanton@sina.com>
2022-10-16 12:42 ` syzbot
[not found] <20221017114136.796-1-hdanton@sina.com>
2022-10-18 1:41 ` syzbot
[not found] <20221018061633.890-1-hdanton@sina.com>
2022-10-18 18:58 ` syzbot
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=00000000000013612005eb2a4525@google.com \
--to=syzbot+69904c3b4a09e8fa2e1b@syzkaller.appspotmail.com \
--cc=a@unstable.cc \
--cc=alsa-devel@alsa-project.org \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=broonie@kernel.org \
--cc=davem@davemloft.net \
--cc=dvyukov@google.com \
--cc=edumazet@google.com \
--cc=hdanton@sina.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mareklindner@neomailbox.ch \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=perex@perex.cz \
--cc=povik+lin@cutebit.org \
--cc=steve@sk2.org \
--cc=sven@narfation.org \
--cc=sw@simonwunderlich.de \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=tiwai@suse.com \
--cc=tonymarislogistics@yandex.com \
--cc=xiyou.wangcong@gmail.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.