From: Oliver Neukum <oneukum@suse.com>
To: syzbot <syzbot+2051460e19471eeb42c3@syzkaller.appspotmail.com>,
gregkh@linuxfoundation.org, johan@kernel.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 15:41:59 +0200 [thread overview]
Message-ID: <badd4d94-2e84-400f-bddc-c9ac8fd6e7c8@suse.com> (raw)
In-Reply-To: <6a6cd832.1aa927e4.17d4bf.0007.GAE@google.com>
[-- Attachment #1: Type: text/plain, Size: 140 bytes --]
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
[-- Attachment #2: 0001-usb-serial-digi_accelport-annotate-spinlocks.patch --]
[-- Type: text/x-patch, Size: 1115 bytes --]
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.
Signed-off-by: Oliver Neukum <oneukum@suse.com>
---
drivers/usb/serial/digi_acceleport.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/serial/digi_acceleport.c b/drivers/usb/serial/digi_acceleport.c
index dea039163661..a687217eadd7 100644
--- a/drivers/usb/serial/digi_acceleport.c
+++ b/drivers/usb/serial/digi_acceleport.c
@@ -522,7 +522,7 @@ static int digi_set_modem_signals(struct usb_serial_port *port,
port_priv->dp_port_num, modem_signals);
spin_lock_irqsave(&oob_priv->dp_port_lock, flags);
- spin_lock(&port_priv->dp_port_lock);
+ spin_lock_nested(&port_priv->dp_port_lock, SINGLE_DEPTH_NESTING);
while (oob_priv->dp_write_urb_in_use) {
spin_unlock(&port_priv->dp_port_lock);
--
2.55.0
next prev parent reply other threads:[~2026-08-04 13:42 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 [this message]
2026-08-04 14:39 ` Johan Hovold
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=badd4d94-2e84-400f-bddc-c9ac8fd6e7c8@suse.com \
--to=oneukum@suse.com \
--cc=gregkh@linuxfoundation.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--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