| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <s5ha79rph1j.wl-tiwai@suse.de>
Date: Wed, 23 Oct 2019 18:23:20 +0200
From: Takashi Iwai <tiwai@...e.de>
To: Jerome Brunet <jbrunet@...libre.com>
Cc: Mark Brown <broonie@...nel.org>,
Liam Girdwood <lgirdwood@...il.com>,
alsa-devel@...a-project.org,
Russell King <rmk+kernel@...linux.org.uk>,
linux-kernel@...r.kernel.org
Subject: Re: [alsa-devel] [PATCH 0/2] ASoC: hdmi-codec: fix locking issue
On Wed, 23 Oct 2019 18:12:01 +0200,
Jerome Brunet wrote:
>
> This patchset fixes the locking issue reported by Russell.
>
> As explained a mutex was used as flag and held while returning to
> userspace.
>
> Patch 2 is entirely optional and switches from bit atomic operation
> to mutex again. I tend to prefer bit atomic operation in this
> particular case but either way should be fine.
I fail to see why the mutex is needed there. Could you elaborate
about the background?
IIUC, the protection with the atomic bitmap should guarantee the
exclusive access. The mutex would allow the possible concurrent calls
of multiple startup of a single instance, but is this the thing to be
solved?
thanks,
Takashi
>
> Jerome Brunet (2):
> Revert "ASoC: hdmi-codec: re-introduce mutex locking"
> ASoC: hdmi-codec: re-introduce mutex locking again
>
> sound/soc/codecs/hdmi-codec.c | 15 +++++++++++----
> 1 file changed, 11 insertions(+), 4 deletions(-)
>
> --
> 2.21.0
>
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@...a-project.org
> https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>
Powered by blists - more mailing lists