From: Peter Zijlstra <peterz@infradead.org>
To: "J. R. Okajima" <hooanon05@yahoo.co.jp>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
Christoph Hellwig <hch@infradead.org>,
Nick Piggin <npiggin@suse.de>,
linux-kernel@vger.kernel.org
Subject: Re: Q. locking order of dcache_lru_lock
Date: Mon, 11 Apr 2011 14:41:24 +0200 [thread overview]
Message-ID: <1302525684.2388.90.camel@twins> (raw)
In-Reply-To: <9823.1302525232@jrobl>
On Mon, 2011-04-11 at 21:33 +0900, J. R. Okajima wrote:
> Peter Zijlstra:
> > Not really a problem, locking order is simply a tool/scheme to avoid
> > deadlocks. Since there is no deadlock potential its fine to 'violate'
> > locking order.
>
> I see.
> Then lockdep always ignore all tyrlocks?
For tracking dependencies, yes. It does register we hold the lock when
the trylock is successful.
prev parent reply other threads:[~2011-04-11 12:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-08 13:20 Q. locking order of dcache_lru_lock J. R. Okajima
2011-04-09 17:12 ` Peter Zijlstra
2011-04-11 5:09 ` J. R. Okajima
2011-04-11 6:27 ` Dave Chinner
2011-04-11 8:30 ` Peter Zijlstra
2011-04-11 12:33 ` J. R. Okajima
2011-04-11 12:41 ` Peter Zijlstra [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=1302525684.2388.90.camel@twins \
--to=peterz@infradead.org \
--cc=hch@infradead.org \
--cc=hooanon05@yahoo.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@suse.de \
--cc=viro@zeniv.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.