From: syzbot <syzbot+6969434de600a6ba9f07@syzkaller.appspotmail.com>
To: alsa-devel@alsa-project.org, broonie@kernel.org, lenb@kernel.org,
lgirdwood@gmail.com, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org, oder_chiou@realtek.com,
perex@perex.cz, rafael@kernel.org, shumingf@realtek.com,
syzkaller-bugs@googlegroups.com, tiwai@suse.com
Subject: Re: [syzbot] [kernel?] INFO: rcu detected stall in sys_wait4 (4)
Date: Thu, 09 May 2024 07:36:02 -0700 [thread overview]
Message-ID: <000000000000a2dd340618065661@google.com> (raw)
In-Reply-To: <0000000000008ac77c0615d60760@google.com>
syzbot has bisected this issue to:
commit 51ea51b18904cd1a0fb244ce41dfd903c2ada628
Author: Shuming Fan <shumingf@realtek.com>
Date: Fri Dec 23 05:58:46 2022 +0000
ASoC: rt711-sdca: add jack detection mode for JD2 100K
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=123e6f88980000
start commit: fe46a7dd189e Merge tag 'sound-6.9-rc1' of git://git.kernel..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=113e6f88980000
console output: https://syzkaller.appspot.com/x/log.txt?x=163e6f88980000
kernel config: https://syzkaller.appspot.com/x/.config?x=fe78468a74fdc3b7
dashboard link: https://syzkaller.appspot.com/bug?extid=6969434de600a6ba9f07
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1091a5f6180000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17a22c13180000
Reported-by: syzbot+6969434de600a6ba9f07@syzkaller.appspotmail.com
Fixes: 51ea51b18904 ("ASoC: rt711-sdca: add jack detection mode for JD2 100K")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next parent reply other threads:[~2024-05-09 14:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0000000000008ac77c0615d60760@google.com>
2024-05-09 14:36 ` syzbot [this message]
2024-07-11 11:11 ` [syzbot] [mm?] INFO: rcu detected stall in sys_wait4 (4) 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=000000000000a2dd340618065661@google.com \
--to=syzbot+6969434de600a6ba9f07@syzkaller.appspotmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lenb@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oder_chiou@realtek.com \
--cc=perex@perex.cz \
--cc=rafael@kernel.org \
--cc=shumingf@realtek.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tiwai@suse.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