From: Toshi Kani <toshi.kani@hp.com>
To: Tang Chen <tangchen@cn.fujitsu.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, dave@sr71.net,
isimatu.yasuaki@jp.fujitsu.com,
vasilis.liaskovitis@profitbricks.com
Subject: Re: [PATCH] mm/hotplug: Verify hotplug memory range
Date: Fri, 09 Aug 2013 09:33:11 -0600 [thread overview]
Message-ID: <1376062391.10300.245.camel@misato.fc.hp.com> (raw)
In-Reply-To: <5204838E.1060602@cn.fujitsu.com>
On Fri, 2013-08-09 at 13:52 +0800, Tang Chen wrote:
> On 08/09/2013 12:47 AM, Toshi Kani wrote:
> > add_memory() and remove_memory() can only handle a memory range aligned
> > with section. There are problems when an unaligned range is added and
> > then deleted as follows:
> >
> > - add_memory() with an unaligned range succeeds, but __add_pages()
> > called from add_memory() adds a whole section of pages even though
> > a given memory range is less than the section size.
> > - remove_memory() to the added unaligned range hits BUG_ON() in
> > __remove_pages().
> >
> > This patch changes add_memory() and remove_memory() to check if a given
> > memory range is aligned with section at the beginning. As the result,
> > add_memory() fails with -EINVAL when a given range is unaligned, and
> > does not add such memory range. This prevents remove_memory() to be
> > called with an unaligned range as well. Note that remove_memory() has
> > to use BUG_ON() since this function cannot fail.
> >
> > Signed-off-by: Toshi Kani<toshi.kani@hp.com>
> > ---
> > mm/memory_hotplug.c | 22 ++++++++++++++++++++++
> > 1 file changed, 22 insertions(+)
> >
> > diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
> > index ca1dd3a..ac182de 100644
> > --- a/mm/memory_hotplug.c
> > +++ b/mm/memory_hotplug.c
> > @@ -1069,6 +1069,22 @@ out:
> > return ret;
> > }
> >
> > +static int check_hotplug_memory_range(u64 start, u64 size)
> > +{
> > + u64 start_pfn = start>> PAGE_SHIFT;
> > + u64 nr_pages = size>> PAGE_SHIFT;
> > +
> > + /* Memory range must be aligned with section */
> > + if ((start_pfn& ~PAGE_SECTION_MASK) ||
> > + (nr_pages % PAGES_PER_SECTION) || (!nr_pages)) {
> > + pr_err("Unsupported hotplug range: start 0x%llx, size 0x%llx\n",
> > + start, size);
>
> I think the message here should tell users that only support range aligned
> to section. Others seems OK to me.
OK, I will change the message to something like this:
pr_err("Section-unaligned hotplug range: start 0x%llx, size 0x%llx\n",
start, size);
> Reviewed-by: Tang Chen <tangchen@cn.fujitsu.com>
Thanks!
-Toshi
--
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:[~2013-08-09 15:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-08 16:47 Toshi Kani
2013-08-08 19:53 ` KOSAKI Motohiro
2013-08-08 19:59 ` Toshi Kani
2013-08-09 5:52 ` Tang Chen
2013-08-09 15:33 ` Toshi Kani [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=1376062391.10300.245.camel@misato.fc.hp.com \
--to=toshi.kani@hp.com \
--cc=akpm@linux-foundation.org \
--cc=dave@sr71.net \
--cc=isimatu.yasuaki@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=tangchen@cn.fujitsu.com \
--cc=vasilis.liaskovitis@profitbricks.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