From: Jiri Slaby <jirislaby@gmail.com>
To: Arjan van de Ven <arjan@linux.intel.com>
Cc: Andrew Morton <akpm@osdl.org>,
alsa-devel@alsa-project.org, Takashi Iwai <tiwai@suse.de>,
James@superbug.demon.co.uk, linux-kernel@vger.kernel.org,
emu10k1-devel@lists.sourceforge.net, perex@suse.cz
Subject: Re: BUG: possible deadlock detected! (sound) [Was: 2.6.17-rc5-mm1]
Date: Thu, 01 Jun 2006 17:27:20 +0159 [thread overview]
Message-ID: <447F076F.9020209@gmail.com> (raw)
In-Reply-To: <1148993947.3636.61.camel@laptopd505.fenrus.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Arjan van de Ven napsal(a):
> On Tue, 2006-05-30 at 14:44 +0200, Takashi Iwai wrote:
>> This ops is a unique object assigned to a different "id" string.
>>
>> The first snd_seq_device_register_driver() called from emu10k1_synth.c
>> is the registration for the id "snd-synth-emu10k1".
>> Then in init_device(), the corresponding devices are initialized, and
>> one callback registers again another device for OSS sequencer with a
>> different id "snd-seq-oss" via snd_seq_device_new() inside the lock.
>> Now it hits the lock-detector but the lock should belong to a
>> different ops object in practice.
>>
>> This nested lock may happen only in two drivers, emu10k1-synth and
>> opl3, and only together with OSS emulation. Since the OSS emulation
>> layer don't do active registration from itself, no deadlock should
>> happen (in theory -- I may oversee something :)
>
> ok fair enough
>
> Jiri, can you test the patch below? (I don't have this hardware)
It's gone in 2.6.17-rc5-mm2.
>
> The ops structure has complex locking rules, where not all ops are
> equal, some are subordinate on others for some complex sound cards. This
> requires for lockdep checking that each individual reg_mutex is
> considered in separation for its locking rules.
>
> Signed-off-by: Arjan van de Ven <arjan@linux.intel.com>
>
> ---
> sound/core/seq/seq_device.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> Index: linux-2.6.17-rc4-mm3-lockdep/sound/core/seq/seq_device.c
> ===================================================================
> --- linux-2.6.17-rc4-mm3-lockdep.orig/sound/core/seq/seq_device.c
> +++ linux-2.6.17-rc4-mm3-lockdep/sound/core/seq/seq_device.c
> @@ -46,6 +46,7 @@
> #include <linux/kmod.h>
> #include <linux/slab.h>
> #include <linux/mutex.h>
> +#include <linux/lockdep.h>
>
> MODULE_AUTHOR("Takashi Iwai <tiwai@suse.de>");
> MODULE_DESCRIPTION("ALSA sequencer device management");
> @@ -73,6 +74,8 @@ struct ops_list {
> struct mutex reg_mutex;
>
> struct list_head list; /* next driver */
> +
> + struct lockdep_type_key reg_mutex_key;
> };
>
>
> @@ -379,7 +382,7 @@ static struct ops_list * create_driver(c
>
> /* set up driver entry */
> strlcpy(ops->id, id, sizeof(ops->id));
> - mutex_init(&ops->reg_mutex);
> + mutex_init_key(&ops->reg_mutex, id, &ops->reg_mutex_key);
> ops->driver = DRIVER_EMPTY;
> INIT_LIST_HEAD(&ops->dev_list);
> /* lock this instance */
>
>
regards,
- --
Jiri Slaby www.fi.muni.cz/~xslaby
\_.-^-._ jirislaby@gmail.com _.-^-._/
B67499670407CE62ACC8 22A032CC55C339D47A7E
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFEfwdvMsxVwznUen4RAohGAKCChQYCo4EPEG0CWDPcld15mZnWTwCeKU+2
l26ws9ExkuBo1wlT5nJ+uWg=
=vgxE
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2006-06-01 15:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060530022925.8a67b613.akpm@osdl.org>
2006-05-30 10:48 ` BUG: possible deadlock detected! (sound) [Was: 2.6.17-rc5-mm1] Jiri Slaby
2006-05-30 11:06 ` Arjan van de Ven
2006-05-30 12:44 ` Takashi Iwai
[not found] ` <s5h3berd6ne.wl%tiwai@suse.de>
2006-05-30 12:59 ` Arjan van de Ven
2006-05-30 13:09 ` Jiri Slaby
2006-06-01 15:28 ` Jiri Slaby [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=447F076F.9020209@gmail.com \
--to=jirislaby@gmail.com \
--cc=James@superbug.demon.co.uk \
--cc=akpm@osdl.org \
--cc=alsa-devel@alsa-project.org \
--cc=arjan@linux.intel.com \
--cc=emu10k1-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@suse.cz \
--cc=tiwai@suse.de \
/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