From: andrew banman <abanman@sgi.com>
To: Andrew Banman <abanman@sgi.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Russ Anderson <rja@sgi.com>, Alex Thorlton <athorlton@sgi.com>,
Yinghai Lu <yinghai@kernel.org>, Greg KH <greg@kroah.com>,
Seth Jennings <sjennings@variantweb.net>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drivers: memory: check for missing sections in test_pages_in_a_zone
Date: Fri, 11 Dec 2015 16:52:54 -0600 [thread overview]
Message-ID: <20151211225254.GG70077@asylum.americas.sgi.com> (raw)
In-Reply-To: <1449872463-4695-1-git-send-email-abanman@sgi.com>
On Fri, Dec 11, 2015 at 04:21:03PM -0600, Andrew Banman wrote:
> test_pages_in_a_zone does not account for the possibility of missing
> sections in the given pfn range. pfn_valid_within always returns 1 when
> CONFIG_HOLES_IN_ZONE is not set, allowing invalid pfns from missing
> sections to pass the test, leading to a kernel oops.
>
> Wrap an additional pfn loop with PAGES_PER_SECTION granularity to check
> for missing sections before proceeding into the zone-check code.
>
> This also prevents a crash from offlining memory devices with missing
> sections. Despite this, it may be a good idea to keep the related patch
> '[PATCH 3/3] drivers: memory: prohibit offlining of memory blocks
> with missing sections' because missing sections in a memory block may lead
> to other problems not covered by the scope of this fix.
>
> ---
Oops, the signed-off-by got absorbed the email headers. I'll resend. The patch
applies cleanly to the current mainline and to the 4.3.2 and 4.2.7 stable
branches. I'll edit the patch description to reflect that as well.
- Andrew
next prev parent reply other threads:[~2015-12-11 22:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-11 22:21 Andrew Banman
2015-12-11 22:52 ` andrew banman [this message]
2015-12-12 1:15 Andrew Banman
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=20151211225254.GG70077@asylum.americas.sgi.com \
--to=abanman@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=athorlton@sgi.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rja@sgi.com \
--cc=sjennings@variantweb.net \
--cc=yinghai@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
all inboxes | Powered by JetHome®