From: Peter Zijlstra <peterz@infradead.org>
To: Ming Lei <ming.lei@canonical.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, Alan Cox <alan@linux.intel.com>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH] tty: tty_mutex: fix lockdep warning in tty_lock_pair(v3)
Date: Sat, 26 May 2012 18:39:45 +0200 [thread overview]
Message-ID: <1338050385.10390.2.camel@laptop> (raw)
In-Reply-To: <CACVXFVNBiXxVvRWxnXiKPRm5dkj6qziFtXA_OH5kYFg4GZ+-pQ@mail.gmail.com>
On Sat, 2012-05-26 at 17:23 +0800, Ming Lei wrote:
>
> You mean that the below is good usage of lock?
>
> LOCK A
> LOCK B
>
> UNLOCK A
> UNLOCK B
Yep, nothing wrong with that. Its lock order that matters, unlock very
much not so.
next prev parent reply other threads:[~2012-05-26 16:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-26 2:54 [PATCH] tty: tty_mutex: fix lockdep warning in tty_lock_pair(v3) Ming Lei
2012-05-26 7:16 ` Peter Zijlstra
2012-05-26 9:23 ` Ming Lei
2012-05-26 16:39 ` Peter Zijlstra [this message]
2012-05-27 4:37 ` Ming Lei
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=1338050385.10390.2.camel@laptop \
--to=peterz@infradead.org \
--cc=alan@linux.intel.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@canonical.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