aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/gpio/max7301.c
diff options
context:
space:
mode:
authorTakashi Iwai <tiwai@suse.de>2012-11-13 11:22:48 +0100
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2012-11-17 13:14:26 -0800
commit093371484195393366f3407465b6f6c53eefdc57 (patch)
treece34cb7f17e83583e48cb2f7ab67ce5280989ab7 /drivers/gpio/max7301.c
parentaaf238baf31e14cb1c111815193c3a78770b1873 (diff)
downloadkernel_samsung_aries-093371484195393366f3407465b6f6c53eefdc57.zip
kernel_samsung_aries-093371484195393366f3407465b6f6c53eefdc57.tar.gz
kernel_samsung_aries-093371484195393366f3407465b6f6c53eefdc57.tar.bz2
ALSA: usb-audio: Fix mutex deadlock at disconnection
commit 10e44239f67d0b6fb74006e61a7e883b8075247a upstream. The recent change for USB-audio disconnection race fixes introduced a mutex deadlock again. There is a circular dependency between chip->shutdown_rwsem and pcm->open_mutex, depicted like below, when a device is opened during the disconnection operation: A. snd_usb_audio_disconnect() -> card.c::register_mutex -> chip->shutdown_rwsem (write) -> snd_card_disconnect() -> pcm.c::register_mutex -> pcm->open_mutex B. snd_pcm_open() -> pcm->open_mutex -> snd_usb_pcm_open() -> chip->shutdown_rwsem (read) Since the chip->shutdown_rwsem protection in the case A is required only for turning on the chip->shutdown flag and it doesn't have to be taken for the whole operation, we can reduce its window in snd_usb_audio_disconnect(). Reported-by: Jiri Slaby <jslaby@suse.cz> Signed-off-by: Takashi Iwai <tiwai@suse.de> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/gpio/max7301.c')
0 files changed, 0 insertions, 0 deletions