From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Guenter Roeck <linux@roeck-us.net>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Sabrina Dubroca <sd@queasysnail.net>
Subject: Re: linux-next: Tree for Feb 13 (runtime failures and 'non-zero nr_pmds' messages)
Date: Sat, 14 Feb 2015 10:37:34 +1100 [thread overview]
Message-ID: <20150214103734.3052cd2f@canb.auug.org.au> (raw)
In-Reply-To: <20150213185428.GA31193@roeck-us.net>
[-- Attachment #1.1: Type: text/plain, Size: 1007 bytes --]
Hi Guenter,
On Fri, 13 Feb 2015 10:54:28 -0800 Guenter Roeck <linux@roeck-us.net> wrote:
>
> I see a number of runtime failures with this version.
> It affects alpha, mips64, ppc64, and x86_64.
> Symptom is always the same. There are lots of
>
> BUG: non-zero nr_pmds on freeing mm: X (where X is 1..4)
>
> messages in the log, and the affected VMs don't reboot.
>
> I don't see the problem in curent mainline, nor in mmotm.
> Bisect points to "Merge branch 'akpm-current/current'",
> which isn't really helpful.
>
> Not sure if this is a bad merge resolution, so just take this
> as a heads-up for now.
Yours is the second report overnight (see attached). Almost certainly
a bad merge resolution on my part (its a bit hard when Andrew get part
of his patch set merged by Linus :-()
I will fix up the merge on Monday (unless Andrew gets more stuff merged
or updates mmotm for me).
Sorry about that.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #1.2: Type: message/rfc822, Size: 2214 bytes --]
From: Sabrina Dubroca <sd@queasysnail.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Subject: Re: linux-next: Tree for Feb 13
Date: Fri, 13 Feb 2015 12:03:26 +0100
Message-ID: <20150213110326.GA26177@kria>
2015-02-13, 16:56:15 +1100, Stephen Rothwell wrote:
> Hi all,
>
> Please do not add any material destined for v3.21 to your linux-next
> included trees until after v3.20-rc1 has been released.
>
> Changes since 20150212:
Hi Stephen,
Your conflict resolution in
8fe7fba50596 "Merge branch 'akpm-current/current'"
for mm/memory.c looks a bit off. I get flooded with these messages:
BUG: non-zero nr_pmds on freeing mm: 4
and fixed it with:
diff --git a/mm/memory.c b/mm/memory.c
index 450e4952c5ef..802adda2b0b6 100644
--- a/mm/memory.c
+++ b/mm/memory.c
@@ -3350,7 +3350,6 @@ int __pmd_alloc(struct mm_struct *mm, pud_t *pud, unsigned long address)
smp_wmb(); /* See comment in __pte_alloc */
spin_lock(&mm->page_table_lock);
- mm_inc_nr_pmds(mm);
#ifndef __ARCH_HAS_4LEVEL_HACK
if (!pud_present(*pud)) {
mm_inc_nr_pmds(mm);
references:
http://www.spinics.net/lists/linux-mm/msg84294.html
dc6c9a35b66b "mm: account pmd page tables to the process"
[CC'ed Kirill A. Shutemov]
Thanks
--
Sabrina
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-02-13 23:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-13 5:56 linux-next: Tree for Feb 13 Stephen Rothwell
2015-02-13 11:03 ` Sabrina Dubroca
2015-02-13 18:18 ` linux-next: Tree for Feb 13 (nfsd) Randy Dunlap
2015-02-13 18:54 ` linux-next: Tree for Feb 13 (runtime failures and 'non-zero nr_pmds' messages) Guenter Roeck
2015-02-13 23:37 ` Stephen Rothwell [this message]
2015-02-14 4:45 ` Guenter Roeck
[not found] ` <20150213165615.1ad43047-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2015-02-14 0:32 ` linux-next: Tree for Feb 13 (iio/magnetometer/ak8975.c) Randy Dunlap
2015-02-14 0:34 ` Randy Dunlap
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=20150214103734.3052cd2f@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=sd@queasysnail.net \
/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).