From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: John Keeping <john@metanate.com>
Cc: Takashi Iwai <tiwai@suse.com>,
"moderated list:SOUND" <alsa-devel@alsa-project.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ALSA: usb-audio: Fix recursive locking on XRUN
Date: Sat, 18 Mar 2023 09:20:05 +0900 [thread overview]
Message-ID: <20230318002005.GA84781@workstation> (raw)
In-Reply-To: <20230317195128.3911155-1-john@metanate.com>
Hi,
On Fri, Mar 17, 2023 at 07:51:27PM +0000, John Keeping wrote:
> snd_usb_queue_pending_output_urbs() may be called from
> snd_pcm_ops::ack() which means the PCM stream is locked.
>
> For the normal case where the call back into the PCM core is via
> prepare_output_urb() the "_under_stream_lock" variant of
> snd_pcm_period_elapsed() is called, but when an error occurs and the
> stream is stopped as XRUN then snd_pcm_xrun() tries to recursively lock
> the stream which results in deadlock.
>
> Follow the example of snd_pcm_period_elapsed() by adding
> snd_pcm_xrun_under_stream_lock() and use this when the PCM substream
> lock is already held.
>
> Signed-off-by: John Keeping <john@metanate.com>
> ---
> include/sound/pcm.h | 1 +
> sound/core/pcm_native.c | 28 ++++++++++++++++++++++++----
> sound/usb/endpoint.c | 18 +++++++++++-------
> 3 files changed, 36 insertions(+), 11 deletions(-)
The name of added kernel API implies me that you refer to existent
'snd_pcm_period_elapsed_under_stream_lock()' which I added to Linux
v5.14.
In my opinion, unlike the version of period elapsed API, the version of
XRUN API seems not to be necessarily required to ALSA PCM core, since PCM
device drivers can implement .pointer callback in the part of PCM operation.
When the callback returns SNDRV_PCM_POS_XRUN, ALSA PCM application get
occurence of XRUN as a result of any operation relevant to hwptr movement
(e.g. SNDRV_PCM_IOCTL_HWSYNC).
Therefore I think it possible to fix the issue without the proposed
kernel API. I can assume some scenario:
1. Failure at tasklet for URB completion
It is softIRQ context. The stream lock is not acquired. It doesn't
matter to call current XRUN API.
2. Failure at PCM operation called by ALSA PCM application
It is process context. The stream lock is acquired before calling driver
code. When detecting any type of failure, driver code stores the state.
Then .pointer callback should return SNDRV_PCM_IOCTL_HWSYNC refering to
the state.
Of course, I'm not a developer for USB audio devices. I'm just a developer
for the other type of packet-oriented drivers (IEC 61883-1/6 packet
streaming engine for audio and music unit in IEEE 1394 bus). So I do not
get every part of USB driver. However, from my experience for the
packet-oriented drivers, I have the above concern about adding the new
XRUN API.
I apologize if miss-hitting the point for your issue.
Regards
Takashi Sakamoto
next prev parent reply other threads:[~2023-03-18 0:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 19:51 [PATCH] ALSA: usb-audio: Fix recursive locking on XRUN John Keeping
2023-03-18 0:20 ` Takashi Sakamoto [this message]
2023-03-18 10:59 ` Takashi Sakamoto
2023-03-19 3:28 ` Takashi Sakamoto
2023-03-19 7:57 ` Takashi Iwai
2023-03-19 9:15 ` Takashi Iwai
2023-03-20 12:04 ` John Keeping
2023-03-20 14:28 ` Takashi Iwai
2023-03-18 2:29 ` kernel test robot
2023-03-18 5:46 ` kernel test robot
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=20230318002005.GA84781@workstation \
--to=o-takashi@sakamocchi.jp \
--cc=alsa-devel@alsa-project.org \
--cc=john@metanate.com \
--cc=linux-kernel@vger.kernel.org \
--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