linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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	[thread overview]
Message-ID: <20150213110326.GA26177@kria> (raw)
In-Reply-To: <20150213165615.1ad43047@canb.auug.org.au>

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

  reply	other threads:[~2015-02-13 11:03 UTC|newest]

Thread overview: 23+ 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 [this message]
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
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
  -- strict thread matches above, loose matches on Subject: below --
2025-02-13  5:33 linux-next: Tree for Feb 13 Stephen Rothwell
2024-02-13  4:08 Stephen Rothwell
2023-02-13  4:33 Stephen Rothwell
2020-02-13  3:52 Stephen Rothwell
2019-02-13  7:39 Stephen Rothwell
2018-02-13  4:15 Stephen Rothwell
2017-02-13  6:36 Stephen Rothwell
2014-02-13  5:38 Stephen Rothwell
2013-02-13  8:35 Stephen Rothwell
2012-02-13  6:26 Stephen Rothwell
2012-02-13 22:10 ` Grant Likely
2012-02-13 23:01 ` Nicholas A. Bellinger
2012-02-13 23:43   ` Stephen Rothwell
2012-02-13 23:32 ` Jack Stone
2012-02-13 23:56 ` Jack Stone

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=20150213110326.GA26177@kria \
    --to=sd@queasysnail.net \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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).