From: Nick Piggin <npiggin@suse.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: agl@us.ibm.com, nacc@us.ibm.com,
Linux Memory Management List <linux-mm@kvack.org>,
kosaki.motohiro@jp.fujitsu.com
Subject: Re: [patch] hugetlb: fix lockdep error
Date: Thu, 29 May 2008 05:26:58 +0200 [thread overview]
Message-ID: <20080529032658.GH3258@wotan.suse.de> (raw)
In-Reply-To: <20080528201929.cf766924.akpm@linux-foundation.org>
On Wed, May 28, 2008 at 08:19:29PM -0700, Andrew Morton wrote:
> On Thu, 29 May 2008 05:07:45 +0200 Nick Piggin <npiggin@suse.de> wrote:
>
> > > > mm/hugetlb.c | 2 +-
> > > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > > >
> > > > Index: linux-2.6/mm/hugetlb.c
> > > > ===================================================================
> > > > --- linux-2.6.orig/mm/hugetlb.c
> > > > +++ linux-2.6/mm/hugetlb.c
> > > > @@ -785,7 +785,7 @@ int copy_hugetlb_page_range(struct mm_st
> > > > continue;
> > > >
> > > > spin_lock(&dst->page_table_lock);
> > > > - spin_lock(&src->page_table_lock);
> > > > + spin_lock_nested(&src->page_table_lock, SINGLE_DEPTH_NESTING);
> > > > if (!huge_pte_none(huge_ptep_get(src_pte))) {
> > > > if (cow)
> > > > huge_ptep_set_wrprotect(src, addr, src_pte);
> > >
> > > Confused. This code has been there since October 2005. Why are we
> > > only seeing lockdep warnings now?
> >
> > Can't say. Haven't looked at hugetlb code or tested it much until now.
> > I am using a recent libhugetlbfs test suite, FWIW.
>
> I don't believe that it's possible that nobody has run that test suite
> with lockdep enabled at any time in the past three years.
Could be it was ignored as a false positive?
> If that's really the case then perhaps we should make the ability to
> recite Documentation/SubmitChecklist in three languages a prerequisite
> for MM development.
It does seem unusual, I don't know...
Would it help to have a big button in kconfig called "test your kernel
patches with this", which then selects various other things?
--
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>
next prev parent reply other threads:[~2008-05-29 3:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080529015956.GC3258@wotan.suse.de>
[not found] ` <20080528191657.ba5f283c.akpm@linux-foundation.org>
2008-05-29 2:29 ` [patch] hugetlb: fix lockdep error Nick Piggin
2008-05-29 2:38 ` Andrew Morton
2008-05-29 3:07 ` Nick Piggin
2008-05-29 3:19 ` Andrew Morton
2008-05-29 3:26 ` Nick Piggin [this message]
2008-05-29 3:35 ` Andrew Morton
2008-05-29 3:48 ` Nish Aravamudan
2008-05-29 8:58 ` Nick Piggin
2008-05-29 12:35 ` Adam Litke
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=20080529032658.GH3258@wotan.suse.de \
--to=npiggin@suse.de \
--cc=agl@us.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=nacc@us.ibm.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;
as well as URLs for NNTP newsgroup(s).