From: Arjan van de Ven <arjan@infradead.org>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org, adobriyan@sw.ru,
peterz@infradead.org, Dave Hansen <haveblue@us.ibm.com>
Subject: Re: [PATCH] make lockdep happy with r/o bind mounts
Date: Mon, 24 Sep 2007 12:52:30 -0700 [thread overview]
Message-ID: <20070924125230.0f144a84@laptopd505.fenrus.org> (raw)
In-Reply-To: <20070924174658.2B3D54B8@kernel>
On Mon, 24 Sep 2007 10:46:58 -0700
Dave Hansen <haveblue@us.ibm.com> wrote:
>
> With the r/o bind mount patches, we can have as many
> spinlocks nested as there are CPUs on the system.
> Lockdep freaks out after 8.
The patch implements the right solution for this "invent your own lock"
situation...
Acked-by: Arjan van de Ven <arjan@linux.intel.com>
prev parent reply other threads:[~2007-09-24 18:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-24 17:46 Dave Hansen
2007-09-24 19:14 ` Peter Zijlstra
2007-09-24 19:52 ` Arjan van de Ven [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=20070924125230.0f144a84@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=adobriyan@sw.ru \
--cc=akpm@osdl.org \
--cc=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
/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®