From: Dave Hansen <haveblue@us.ibm.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Alexey Dobriyan <adobriyan@sw.ru>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.23-rc7-mm1: r/o mounts joke with lockdep
Date: Mon, 24 Sep 2007 09:33:00 -0700 [thread overview]
Message-ID: <1190651581.26982.230.camel@localhost> (raw)
In-Reply-To: <20070924092658.91c17511.akpm@linux-foundation.org>
On Mon, 2007-09-24 at 09:26 -0700, Andrew Morton wrote:
> On Mon, 24 Sep 2007 13:51:05 +0400 Alexey Dobriyan <adobriyan@sw.ru> wrote:
>
> > static void lock_and_coalesce_cpu_mnt_writer_counts(void)
> > {
> > int cpu;
> > struct mnt_writer *cpu_writer;
> >
> > for_each_possible_cpu(cpu) {
> > cpu_writer = &per_cpu(mnt_writers, cpu);
> > spin_lock_nested(&cpu_writer->lock, 42);
> > ^^^^
> >
> > What the heck is going on?
>
> that was some random 2:00AM hack by me to make the warnings go away.
>
> > Given that MAX_LOCKDEP_SUBCLASSES is only 8,
> > this reliably turns off lockdep at boot.
>
> that explains why it worked so well.
Arjan gave me some ideas on how to fix this more properly. I'm trying
to reproduce it and working on a patch now.
-- Dave
prev parent reply other threads:[~2007-09-24 16:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-24 9:51 2.6.23-rc7-mm1: r/o mounts joke with lockdep Alexey Dobriyan
2007-09-24 16:26 ` Andrew Morton
2007-09-24 16:33 ` Dave Hansen [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=1190651581.26982.230.camel@localhost \
--to=haveblue@us.ibm.com \
--cc=adobriyan@sw.ru \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.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