From: Mel Gorman <mgorman@suse.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Wilcox, Matthew R" <matthew.r.wilcox@intel.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
Rik van Riel <riel@redhat.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH] mm: Actually clear pmd_numa before invalidating
Date: Wed, 13 Aug 2014 22:18:34 +0100 [thread overview]
Message-ID: <20140813211834.GJ7970@suse.de> (raw)
In-Reply-To: <20140813132333.92f2ade49867acbfb9ed696b@linux-foundation.org>
On Wed, Aug 13, 2014 at 01:23:33PM -0700, Andrew Morton wrote:
> On Wed, 13 Aug 2014 20:16:31 +0000 "Wilcox, Matthew R" <matthew.r.wilcox@intel.com> wrote:
>
> > I am quite shockingly ignorant of the MM code. While looking at this
> > function to figure out how/whether to use it, I noticed the bug, and
> > sent a patch. I assumed the gibberish in the changelog meant something
> > important to people who actually understand this part of the kernel :-)
>
> Fair enough ;) Mel?
The issue was theoritical in nature. The patch was meant to guarantee
the PTE was in a known state. As I cannot think of a way it could
trigger a bug I wouldn't consider it -stable material but Matthew's
patch is still doing the expected thing.
--
Mel Gorman
SUSE Labs
--
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>
prev parent reply other threads:[~2014-08-13 21:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-13 15:28 [PATCH] mm: Actually clear pmd_numa before invalidating Matthew Wilcox
2014-08-13 15:56 ` Rik van Riel
2014-08-13 16:32 ` Mel Gorman
2014-08-13 19:59 ` Andrew Morton
2014-08-13 20:04 ` Wilcox, Matthew R
2014-08-13 20:12 ` Andrew Morton
2014-08-13 20:16 ` Wilcox, Matthew R
2014-08-13 20:23 ` Andrew Morton
2014-08-13 21:18 ` Mel Gorman [this message]
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=20140813211834.GJ7970@suse.de \
--to=mgorman@suse.de \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=matthew.r.wilcox@intel.com \
--cc=riel@redhat.com \
--cc=stable@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).