From: Hugh Dickins <hughd@google.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Andrea Arcangeli <aarcange@redhat.com>, linux-mm@kvack.org
Subject: Re: [PATCH] mm: fix UP THP spin_is_locked BUGs
Date: Tue, 7 Feb 2012 16:33:18 -0800 (PST) [thread overview]
Message-ID: <alpine.LSU.2.00.1202071616390.16273@eggly.anvils> (raw)
In-Reply-To: <20120207161209.52d065e1.akpm@linux-foundation.org>
On Tue, 7 Feb 2012, Andrew Morton wrote:
> On Tue, 7 Feb 2012 16:00:46 -0800 (PST)
> Hugh Dickins <hughd@google.com> wrote:
>
> > +++ linux/mm/huge_memory.c 2012-02-07 15:37:18.581666053 -0800
> > @@ -2083,7 +2083,7 @@ static void collect_mm_slot(struct mm_sl
> > {
> > struct mm_struct *mm = mm_slot->mm;
> >
> > - VM_BUG_ON(!spin_is_locked(&khugepaged_mm_lock));
> > + VM_BUG_ON(NR_CPUS != 1 && !spin_is_locked(&khugepaged_mm_lock));
>
> We do have assert_spin_locked(), but I couldn't see any way of using it
> while observing these laziness constraints ;)
;) I didn't know about assert_spin_locked(). Hmm, fs/dcache.c seems
to be using that successfully. We could forget about the VM_ part of
it and respin the patch with assert_spin_locked(). I don't really
mind either way: but happy to let laziness win the day - I'm back
on an SMP kernel by now anyway.
>
> Should we patch -stable too?
People seem to have survived very well without it so far, I think
it's an unusual config combination, and quickly obvious if anyone
hits it. But I've no objection if you think it deserves -stable.
Hugh
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2012-02-08 0:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-08 0:00 Hugh Dickins
2012-02-08 0:12 ` Andrew Morton
2012-02-08 0:33 ` Hugh Dickins [this message]
2012-02-08 2:35 ` Andrew Morton
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=alpine.LSU.2.00.1202071616390.16273@eggly.anvils \
--to=hughd@google.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.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