linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Gerald Schaefer <gerald.schaefer@de.ibm.com>
Cc: David Rientjes <rientjes@google.com>,
	Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>,
	Hugh Dickins <hughd@google.com>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	Michal Hocko <mhocko@suse.cz>,
	Andrea Arcangeli <aarcange@redhat.com>,
	Martin Schwidefsky <schwidefsky@de.ibm.com>,
	Jiri Slaby <jslaby@suse.cz>
Subject: Re: [PATCH] mm/hugetlb: use pmd_page() in follow_huge_pmd()
Date: Fri, 10 Apr 2015 13:38:59 -0700	[thread overview]
Message-ID: <20150410133859.fc79985a9514eb1e4d1dcde7@linux-foundation.org> (raw)
In-Reply-To: <20150410100849.56b9d677@thinkpad>

On Fri, 10 Apr 2015 10:08:49 +0200 Gerald Schaefer <gerald.schaefer@de.ibm.com> wrote:

> On Thu, 9 Apr 2015 12:41:47 -0700 (PDT)
> David Rientjes <rientjes@google.com> wrote:
> 
> > On Thu, 9 Apr 2015, Gerald Schaefer wrote:
> > 
> > > commit 61f77eda "mm/hugetlb: reduce arch dependent code around
> > > follow_huge_*" broke follow_huge_pmd() on s390, where pmd and pte
> > > layout differ and using pte_page() on a huge pmd will return wrong
> > > results. Using pmd_page() instead fixes this.
> > > 
> > > All architectures that were touched by commit 61f77eda have
> > > pmd_page() defined, so this should not break anything on other
> > > architectures.
> > > 
> > > Signed-off-by: Gerald Schaefer <gerald.schaefer@de.ibm.com>
> > > Cc: stable@vger.kernel.org # v3.12
> > 
> > Acked-by: David Rientjes <rientjes@google.com>
> > 
> > I'm not sure where the stable cc came from, though: commit 61f77eda
> > makes s390 use a generic version of follow_huge_pmd() and that
> > generic version is buggy for s930 because of commit e66f17ff7177
> > ("mm/hugetlb: take page table lock in follow_huge_pmd()").  Both of
> > those are 4.0 material, though, so why is this needed for stable 3.12?
> 
> Both commits 61f77eda and e66f17ff already made it into the 3.12 stable
> tree, probably because of SLES 12 (actually that's how I noticed them).
> 
> But I guess I screwed up the stable CC, stable@vger.kernel.org.#.v3.12
> somehow doesn't look right, not sure if the CC in the patch header
> suffices. Looks like Jiri Slaby added the patches to 3.12, putting him
> on CC now.

hm.  I think I'll make it

Fixes: 61f77eda "mm/hugetlb: reduce arch dependent code around follow_huge_*"
...
Cc: <stable@vger.kernel.org>

There's enough info here for the various tree maintainers to work out
whether their kernel needs this fix.

--
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>

  reply	other threads:[~2015-04-10 20:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-09 16:11 Gerald Schaefer
2015-04-09 19:41 ` David Rientjes
2015-04-10  8:08   ` Gerald Schaefer
2015-04-10 20:38     ` Andrew Morton [this message]
2015-04-23  7:46       ` Jiri Slaby
2015-04-10  0:08 ` Naoya Horiguchi

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=20150410133859.fc79985a9514eb1e4d1dcde7@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=aarcange@redhat.com \
    --cc=gerald.schaefer@de.ibm.com \
    --cc=hughd@google.com \
    --cc=jslaby@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.cz \
    --cc=n-horiguchi@ah.jp.nec.com \
    --cc=rientjes@google.com \
    --cc=schwidefsky@de.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