From: Arjan van de Ven <arjan@linux.intel.com>
To: Dmitry Torokhov <dtor_core@ameritech.net>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, mingo@redhat.com,
arjanv@redhat.com, Linux Portal <linportal@gmail.com>
Subject: Re: [patch] Declare explicit, hardware based lock ranking in serio
Date: Sat, 03 Jun 2006 14:11:17 +0200 [thread overview]
Message-ID: <1149336677.3109.34.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <200606030756.39861.dtor_core@ameritech.net>
On Sat, 2006-06-03 at 07:56 -0400, Dmitry Torokhov wrote:
> On Saturday 03 June 2006 04:50, Arjan van de Ven wrote:
> > > Thanks.
> > >
> > > So we're taking ps2->cmd_mutex and then we're recurring back into
> > > ps2_command() and then taking ps2->serio->cmd_mutex.
> > >
> > > I suspect that's all correct/natural/expected and needs another
> > > make-lockdep-shut-up patch.
> >
> >
> > The PS/2 code has a natural device order and there is a one level
> > recursion in this device order in terms of the cmd_mutex; annotate
> > this explicit recursion as ok
> >
>
> It is not necessarily single depth - one could have 2 or more pass-through
> ports chained together, although currently in kernel we only have Synaptics
> pass-through. If we were ever to implement pass-through port for IBMs
> trackpoints then we'd have:
>
> Synaptics<->pass-through<->TP<->pass-through<->some mouse
is there a bound to this? lockdep can deal with upto 8 or so
recursions....
next prev parent reply other threads:[~2006-06-03 12:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-02 16:53 Kernel lock bug detected (kseriod) Linux Portal
2006-06-02 23:13 ` Andrew Morton
2006-06-03 1:52 ` Dmitry Torokhov
2006-06-03 8:50 ` [patch] Declare explicit, hardware based lock ranking in serio Arjan van de Ven
2006-06-03 11:56 ` Dmitry Torokhov
2006-06-03 12:11 ` Arjan van de Ven [this message]
2006-06-03 16:11 ` Dmitry Torokhov
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=1149336677.3109.34.camel@laptopd505.fenrus.org \
--to=arjan@linux.intel.com \
--cc=akpm@osdl.org \
--cc=arjanv@redhat.com \
--cc=dtor_core@ameritech.net \
--cc=linportal@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.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®