From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Jiri Kosina <jikos@jikos.cz>,
Alessandro Suardi <alessandro.suardi@gmail.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: 2.6.18-git21, possible recursive locking in kseriod ends up in DWARF2 unwinder stuck
Date: Fri, 06 Oct 2006 13:38:16 +0200 [thread overview]
Message-ID: <1160134696.2792.102.camel@taijtu> (raw)
In-Reply-To: <d120d5000610051334o7604b1d4hd2f4c9a9b858f06e@mail.gmail.com>
On Thu, 2006-10-05 at 16:34 -0400, Dmitry Torokhov wrote:
> On 10/4/06, Jiri Kosina <jikos@jikos.cz> wrote:
> > On Wed, 4 Oct 2006, Alessandro Suardi wrote:
> >
> > > Non-fatal (box is still alive and apparently well) on boot,
> > > FC5-uptodate on a Dell Latitude C640. From the dmesg ring:
> >
> > > [ 8.680000] =============================================
> > > [ 8.680000] [ INFO: possible recursive locking detected ]
> > > [ 8.680000] 2.6.18-git21 #1
> > > [ 8.680000] ---------------------------------------------
> > > [ 8.680000] kseriod/163 is trying to acquire lock:
> > > [ 8.680000] (&ps2dev->cmd_mutex/1){--..}, at: [<c03198c3>]
> > > ps2_command+0x89/0x358
> >
> > Me and Peter Zijlstra have already submitted patches to fix this - read
> > the thread at
> > http://linux.derkeiler.com/Mailing-Lists/Kernel/2006-09/msg07416.html
> >
> > I don't know the reason why these have not yet been merged into the input
> > tree. Dmitry?
> >
>
> Sorry, was a little busy.
>
> I tested the patches and they work. Couple of comments:
>
> - register_lock_class is marked as inline but now has 2 call sites and
> is relatively big - might want to remove "inline"
> - how about adding lockdep_set_subclass() to avoid littering source
> with struct lock_class_key when we only want to tweak subclass? For
> that we might want export register_lock_class and hide it behind a
> #define...
>
or something like this:
#define concat_i(a) #a
#define concat(a,b) concat_i(a ## b)
#define lockdep_set_subclass(lock, subclass) \
({ static struct lock_key_class __key; \
lockdep_init_map(&(lock)->dep_map, concat(lock, subclass), \
&__key, subclass); })
next prev parent reply other threads:[~2006-10-06 11:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-04 21:17 Alessandro Suardi
2006-10-04 21:25 ` Jiri Kosina
2006-10-05 20:34 ` Dmitry Torokhov
2006-10-06 9:22 ` Jiri Kosina
2006-10-06 11:38 ` Peter Zijlstra [this message]
2006-10-06 13:29 ` Dmitry Torokhov
2006-10-13 6:12 ` Ingo Molnar
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=1160134696.2792.102.camel@taijtu \
--to=a.p.zijlstra@chello.nl \
--cc=alessandro.suardi@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=jikos@jikos.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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
Powered by JetHome