From: Toshi Kani <toshi.kani@hp.com>
To: Wanpeng Li <liwanp@linux.vnet.ibm.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, kosaki.motohiro@jp.fujitsu.com,
kamezawa.hiroyu@jp.fujitsu.com, dave@sr71.net,
isimatu.yasuaki@jp.fujitsu.com, tangchen@cn.fujitsu.com,
vasilis.liaskovitis@profitbricks.com
Subject: Re: [PATCH v2] mm/hotplug: Verify hotplug memory range
Date: Mon, 12 Aug 2013 08:49:28 -0600 [thread overview]
Message-ID: <1376318968.10300.334.camel@misato.fc.hp.com> (raw)
In-Reply-To: <20130811233722.GA27223@hacker.(null)>
On Mon, 2013-08-12 at 07:37 +0800, Wanpeng Li wrote:
> On Sat, Aug 10, 2013 at 01:17:32PM -0600, 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>
> >Acked-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
> >Reviewed-by: Tang Chen <tangchen@cn.fujitsu.com>
>
> Reviewed-by: Wanpeng Li <liwanp@linux.vnet.ibm.com>
Thanks Wanpeng!
-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>
next prev parent reply other threads:[~2013-08-12 14:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-10 19:17 [PATCH v2] mm/hotplug: Verify hotplug memory range Toshi Kani
2013-08-11 23:37 ` Wanpeng Li
2013-08-12 14:49 ` Toshi Kani [this message]
2013-08-11 23:37 ` Wanpeng Li
2013-08-14 22:09 ` Andrew Morton
2013-08-14 23:34 ` Toshi Kani
2013-08-14 23:45 ` Andrew Morton
2013-08-14 23:45 ` Toshi Kani
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=1376318968.10300.334.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=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liwanp@linux.vnet.ibm.com \
--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