From: syzbot <syzbot+d9aa9a4d32dc3976468e@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Forwarded: Re: [syzbot] [comedi?] inconsistent lock state in waveform_ao_cancel
Date: Wed, 25 Feb 2026 05:00:50 -0800 [thread overview]
Message-ID: <699ef282.a00a0220.301b66.0004.GAE@google.com> (raw)
In-Reply-To: <6993bcb7.050a0220.340abe.0778.GAE@google.com>
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.
***
Subject: Re: [syzbot] [comedi?] inconsistent lock state in waveform_ao_cancel
Author: abbotti@mev.co.uk
#syz dup: [syzbot] [comedi?] inconsistent lock state in das16m1_interrupt
prev parent reply other threads:[~2026-02-25 13:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-17 0:56 [syzbot] [comedi?] inconsistent lock state in waveform_ao_cancel syzbot
2026-02-25 13:00 ` syzbot [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=699ef282.a00a0220.301b66.0004.GAE@google.com \
--to=syzbot+d9aa9a4d32dc3976468e@syzkaller.appspotmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox