From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Joel Becker <Joel.Becker@oracle.com>
Cc: Arjan van de Ven <arjan@infradead.org>,
Louis Rilling <Louis.Rilling@kerlabs.com>,
linux-kernel@vger.kernel.org, ocfs2-devel@oss.oracle.com
Subject: Re: [RFC][PATCH 0/3] configfs: Make nested default groups lockdep-friendly
Date: Wed, 21 May 2008 11:20:00 +0200 [thread overview]
Message-ID: <1211361600.6463.65.camel@lappy.programming.kicks-ass.net> (raw)
In-Reply-To: <20080520235138.GL26609@mail.oracle.com>
On Tue, 2008-05-20 at 16:51 -0700, Joel Becker wrote:
> On Tue, May 20, 2008 at 03:35:43PM -0700, Arjan van de Ven wrote:
> > not quite what I meant; what I meant is more like how sched.c deals
> > with per cpu queues:
> >
> > (from sched.c)
> >
> > spin_lock_init(&rq->lock);
> > lockdep_set_class(&rq->lock, &rq->rq_lock_key);
>
> Looking at this, it's taking the address of the struct
> lock_class_key as the actual key. Thus, if we tie one of these guys to
> the structure we're representing, we get lock safety...except that we're
> talking about i_mutex here, and we want to interact with the VFS's use
> thereof.
Also bear in mind that the lock_class_key structure must be in static
storage.
next prev parent reply other threads:[~2008-05-21 9:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-20 16:33 [RFC][PATCH 0/3] configfs: Make nested default groups lockdep-friendly Louis Rilling
2008-05-20 16:33 ` [RFC][PATCH 1/3] configfs: set CONFIGFS_USET_DEFAULT earlier in configfs_attach_group() Louis Rilling
2008-05-20 16:33 ` [RFC][PATCH 2/3] configfs: Silence lockdep when creating nested default groups Louis Rilling
2008-05-20 16:33 ` [RFC][PATCH 3/3] configfs: Silence lockdep when destroying " Louis Rilling
2008-05-20 16:58 ` [RFC][PATCH 0/3] configfs: Make nested default groups lockdep-friendly Arjan van de Ven
2008-05-20 17:08 ` Louis Rilling
2008-05-20 21:56 ` Joel Becker
2008-05-20 22:13 ` Arjan van de Ven
2008-05-20 22:27 ` Joel Becker
2008-05-20 22:35 ` Arjan van de Ven
2008-05-20 23:51 ` Joel Becker
2008-05-21 9:20 ` Peter Zijlstra [this message]
2008-05-21 9:23 ` Peter Zijlstra
2008-05-21 10:25 ` Louis Rilling
2008-05-21 10:59 ` Peter Zijlstra
2008-05-21 12:54 ` Louis Rilling
2008-05-21 22:09 ` Joel Becker
2008-05-21 8:13 ` Louis Rilling
2008-05-20 21:41 ` [Ocfs2-devel] " Joel Becker
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=1211361600.6463.65.camel@lappy.programming.kicks-ass.net \
--to=a.p.zijlstra@chello.nl \
--cc=Joel.Becker@oracle.com \
--cc=Louis.Rilling@kerlabs.com \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ocfs2-devel@oss.oracle.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