From: syzbot <syzbot+18840ef96e57b83b7fea@syzkaller.appspotmail.com>
To: eadavis@qq.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [sound?] possible deadlock in _snd_pcm_stream_lock_irqsave (4)
Date: Wed, 20 Mar 2024 18:54:03 -0700 [thread overview]
Message-ID: <00000000000054ad49061421fbf1@google.com> (raw)
In-Reply-To: <tencent_164B6A74DD764D66063CFF36AE96A2372609@qq.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-and-tested-by: syzbot+18840ef96e57b83b7fea@syzkaller.appspotmail.com
Tested on:
commit: fe46a7dd Merge tag 'sound-6.9-rc1' of git://git.kernel..
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=1268783a180000
kernel config: https://syzkaller.appspot.com/x/.config?x=aef2a55903e5791c
dashboard link: https://syzkaller.appspot.com/bug?extid=18840ef96e57b83b7fea
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=10928f15180000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2024-03-21 1:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-18 19:59 [syzbot] [sound?] possible deadlock in _snd_pcm_stream_lock_irqsave (4) syzbot
2024-03-19 6:40 ` Takashi Iwai
2024-03-21 0:40 ` Edward Adam Davis
2024-03-21 0:42 ` syzbot
2024-03-21 1:30 ` Edward Adam Davis
2024-03-21 1:54 ` syzbot [this message]
2024-03-21 2:22 ` [PATCH] ALSA: timer: fix deadlock in _snd_pcm_stream_lock_irqsave Edward Adam Davis
2024-03-21 6:33 ` Takashi Iwai
2024-03-18 20:09 [syzbot] [sound?] inconsistent lock state in snd_timer_interrupt syzbot
2024-03-21 1:37 ` [syzbot] [sound?] possible deadlock in _snd_pcm_stream_lock_irqsave (4) Edward Adam Davis
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=00000000000054ad49061421fbf1@google.com \
--to=syzbot+18840ef96e57b83b7fea@syzkaller.appspotmail.com \
--cc=eadavis@qq.com \
--cc=linux-kernel@vger.kernel.org \
--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.