From: Oliver Neukum <oneukum@suse.com>
To: Ricardo Ribalda <ribalda@chromium.org>,
Takashi Iwai <tiwai@suse.com>, Len Brown <len.brown@intel.com>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
Kai Vehmanen <kai.vehmanen@linux.intel.com>,
Ranjani Sridharan <ranjani.sridharan@linux.intel.com>,
Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>,
Pavel Machek <pavel@ucw.cz>,
"Rafael J. Wysocki" <rafael@kernel.org>
Cc: alsa-devel@alsa-project.org,
"Joel Fernandes (Google)" <joel@joelfernandes.org>,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH v3 0/2] ALSA: core: Fix deadlock when shutdown a frozen userspace
Date: Mon, 28 Nov 2022 10:26:50 +0100 [thread overview]
Message-ID: <a5504a76-d59f-7b5d-769b-8dd0539681c8@suse.com> (raw)
In-Reply-To: <20221127-snd-freeze-v3-0-a2eda731ca14@chromium.org>
On 28.11.22 10:10, Ricardo Ribalda wrote:
> Since 83bfc7e793b5 ("ASoC: SOF: core: unregister clients and machine drivers in .shutdown")
> we wait for userspace to close its fds.
>
> But that will never occur with a frozen userspace (like during kexec()).
Hi,
that means that user space can delay an unplugging process for an
indefinite time. And that is a problem. I am afraid there is a problem
with the basic approach, even outside of times user space is frozen.
Regards
Oliver
prev parent reply other threads:[~2022-11-28 9:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 9:10 Ricardo Ribalda
2022-11-28 9:10 ` [PATCH v3 1/2] freezer: Add processes_frozen() Ricardo Ribalda
2022-11-28 9:10 ` [PATCH v3 2/2] ALSA: core: Fix deadlock when shutdown a frozen userspace Ricardo Ribalda
2022-11-28 9:24 ` [PATCH v3 0/2] " Takashi Iwai
2022-11-28 9:26 ` Ricardo Ribalda
2022-11-28 9:53 ` Takashi Iwai
2022-11-28 13:34 ` Ricardo Ribalda
2022-11-28 9:26 ` Oliver Neukum [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=a5504a76-d59f-7b5d-769b-8dd0539681c8@suse.com \
--to=oneukum@suse.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=joel@joelfernandes.org \
--cc=kai.vehmanen@linux.intel.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=perex@perex.cz \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=rafael@kernel.org \
--cc=ranjani.sridharan@linux.intel.com \
--cc=ribalda@chromium.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
all inboxes | Powered by JetHome®