linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Nick Piggin <npiggin@suse.de>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [rfc][patch] mm: lockdep page lock
Date: Tue, 16 Mar 2010 07:20:32 +0100	[thread overview]
Message-ID: <20100316062032.GB22651@elte.hu> (raw)
In-Reply-To: <20100315155859.GE2869@laptop>


* Nick Piggin <npiggin@suse.de> wrote:

> Page lock has very complex dependencies, so it would be really nice to add 
> lockdep support for it.

Just wondering - has your patch shown any suspect areas of code already, in 
the testing you did?

Maybe it should be test-driven for a while, in a non-append-only tree such as 
-mm, to see whether it's finding real bugs.

	Ingo

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  parent reply	other threads:[~2010-03-16  6:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-15 15:58 [rfc][patch] mm: lockdep page lock Nick Piggin
2010-03-15 18:08 ` Jan Kara
2010-03-16  2:21   ` Nick Piggin
2010-03-16 11:52     ` Jan Kara
2010-03-24 13:28     ` Peter Zijlstra
2010-03-25  5:36       ` Nick Piggin
2010-03-25  9:40         ` Peter Zijlstra
2010-03-26  3:18       ` Jamie Lokier
2010-03-26  6:54         ` Peter Zijlstra
2010-03-26 11:54           ` Jamie Lokier
2010-03-24 13:54     ` Peter Zijlstra
2010-03-16  6:20 ` Ingo Molnar [this message]
2010-03-16  6:42   ` Nick Piggin

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=20100316062032.GB22651@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=npiggin@suse.de \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    /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;
as well as URLs for NNTP newsgroup(s).