From: Takashi Iwai <tiwai@suse.de>
To: John Keeping <jkeeping@inmusicbrands.com>
Cc: Takashi Iwai <tiwai@suse.com>,
Clemens Ladisch <clemens@ladisch.de>,
Jaroslav Kysela <perex@perex.cz>,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [BUG] ALSA: usb-audio: drain may fail with multi-port close race
Date: Mon, 17 Feb 2025 18:06:16 +0100 [thread overview]
Message-ID: <8734gc8prr.wl-tiwai@suse.de> (raw)
In-Reply-To: <20250217111647.3368132-1-jkeeping@inmusicbrands.com>
On Mon, 17 Feb 2025 12:16:46 +0100,
John Keeping wrote:
>
> I'm seeing a bug where data sometimes fails to send on USB MIDI devices
> with multiple ports which seems to be a result of a race around closing
> ports introduced by commit 0125de38122f0 ("ALSA: usb-audio: Cancel
> pending work at closing a MIDI substream").
>
> The scenario is essentially this program:
>
> snd_rawmidi_t *port0, *port1;
> snd_rawmidi_open(NULL, &port0, "hw:0,0,0", 0);
> snd_rawmidi_open(NULL, &port1, "hw:0,0,1", 0);
>
> snd_rawmidi_write(port0, data, len);
>
> snd_rawmidi_close(port1);
> snd_rawmidi_close(port0);
>
> What happens seems to be the following:
>
> write(port0)
> `- snd_usbmidi_output_trigger
> `- queue_work()
> close(port1)
> `- snd_usbmidi_output_close
> `- cancel_work_sync() # Work has not yet started here
> close(port0)
> `- snd_rawmidi_drain_output
> # Times out because nothing is processing outbound data!
>
> The two ports interact like this because they are on the same endpoint,
> so should the work only be cancelled when the last endpoint is closed?
How about the following patch work?
It's a band-aid, but should suffice. The callback is already
protected with rawmidi open_mutex.
thanks,
Takashi
-- 8< --
--- a/sound/usb/midi.c
+++ b/sound/usb/midi.c
@@ -1144,8 +1144,11 @@ static int snd_usbmidi_output_open(struct snd_rawmidi_substream *substream)
static int snd_usbmidi_output_close(struct snd_rawmidi_substream *substream)
{
struct usbmidi_out_port *port = substream->runtime->private_data;
+ struct snd_usb_midi *umidi = substream->rmidi->private_data;
- cancel_work_sync(&port->ep->work);
+ /* cancel at the last close */
+ if (umidi->opened[0] == 1)
+ cancel_work_sync(&port->ep->work);
return substream_open(substream, 0, 0);
}
next prev parent reply other threads:[~2025-02-17 17:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-17 11:16 [BUG] ALSA: usb-audio: drain may fail with multi-port close race John Keeping
2025-02-17 17:06 ` Takashi Iwai [this message]
2025-02-17 18:38 ` John Keeping
2025-02-18 8:07 ` Takashi Iwai
2025-02-18 10:56 ` John Keeping
2025-02-18 11:39 ` Takashi Iwai
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=8734gc8prr.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=clemens@ladisch.de \
--cc=jkeeping@inmusicbrands.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--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