From: Johan Hovold <johan@kernel.org>
To: Oliver Neukum <oneukum@suse.com>
Cc: syzbot <syzbot+2051460e19471eeb42c3@syzkaller.appspotmail.com>,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [usb?] possible deadlock in digi_set_modem_signals
Date: Tue, 4 Aug 2026 16:39:38 +0200 [thread overview]
Message-ID: <anH5qi4skYbh0iO0@hovoldconsulting.com> (raw)
In-Reply-To: <badd4d94-2e84-400f-bddc-c9ac8fd6e7c8@suse.com>
On Tue, Aug 04, 2026 at 03:41:59PM +0200, Oliver Neukum wrote:
>
>
> On 31.07.26 19:15, syzbot wrote:
> > If you want syzbot to run the reproducer, reply with:
>
> #syz test: git://repo/address.git 11028ab62899
>
> From ce3cda5cc4df748600c37b6b5cf5964d21478e1c Mon Sep 17 00:00:00 2001
> From: Oliver Neukum <oneukum@suse.com>
> Date: Tue, 4 Aug 2026 11:38:30 +0200
> Subject: [PATCH 1/2] usb: serial: digi_accelport: annotate spinlocks
>
> The driver holds two spinlocks at the same time.
> This is perfectly safe, but confuses the validator.
> Tell it manually that we know what we are doing.
I fixed this up a few days ago after I saw the report:
https://lore.kernel.org/all/20260801125827.292983-1-johan@kernel.org/
I've merged that patch for 7.2 to avoid others spending time on it, but
perhaps I should have replied to the report as well. Sorry about that.
Johan
next prev parent reply other threads:[~2026-08-04 14:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 17:15 [syzbot] [usb?] possible deadlock in digi_set_modem_signals syzbot
2026-08-04 13:41 ` Oliver Neukum
2026-08-04 14:39 ` Johan Hovold [this message]
2026-08-04 15:20 ` 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=anH5qi4skYbh0iO0@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=oneukum@suse.com \
--cc=syzbot+2051460e19471eeb42c3@syzkaller.appspotmail.com \
--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