linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [PATCH v2] mm/hotplug: Verify hotplug memory range
@ 2013-08-10 19:17 Toshi Kani
       [not found] ` <20130811233722.GA27223@hacker.(null)>
  2013-08-14 22:09 ` Andrew Morton
  0 siblings, 2 replies; 6+ messages in thread
From: Toshi Kani @ 2013-08-10 19:17 UTC (permalink / raw)
  To: akpm
  Cc: linux-mm, linux-kernel, kosaki.motohiro, kamezawa.hiroyu, dave,
	isimatu.yasuaki, tangchen, vasilis.liaskovitis, Toshi Kani

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>
---
v2: Updated the error message.

---
 mm/memory_hotplug.c |   22 ++++++++++++++++++++++
 1 file changed, 22 insertions(+)

diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
index ca1dd3a..3bb1f39 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("Section-unaligned hotplug range: start 0x%llx, size 0x%llx\n",
+				start, size);
+		return -EINVAL;
+	}
+
+	return 0;
+}
+
 /* we are OK calling __meminit stuff here - we have CONFIG_MEMORY_HOTPLUG */
 int __ref add_memory(int nid, u64 start, u64 size)
 {
@@ -1078,6 +1094,10 @@ int __ref add_memory(int nid, u64 start, u64 size)
 	struct resource *res;
 	int ret;
 
+	ret = check_hotplug_memory_range(start, size);
+	if (ret)
+		return ret;
+
 	lock_memory_hotplug();
 
 	res = register_memory_resource(start, size);
@@ -1786,6 +1806,8 @@ void __ref remove_memory(int nid, u64 start, u64 size)
 {
 	int ret;
 
+	BUG_ON(check_hotplug_memory_range(start, size));
+
 	lock_memory_hotplug();
 
 	/*

^ permalink raw reply related	[flat|nested] 6+ messages in thread

* Re: [PATCH v2] mm/hotplug: Verify hotplug memory range
       [not found] ` <20130811233722.GA27223@hacker.(null)>
@ 2013-08-12 14:49   ` Toshi Kani
  0 siblings, 0 replies; 6+ messages in thread
From: Toshi Kani @ 2013-08-12 14:49 UTC (permalink / raw)
  To: Wanpeng Li
  Cc: akpm, linux-mm, linux-kernel, kosaki.motohiro, kamezawa.hiroyu,
	dave, isimatu.yasuaki, tangchen, vasilis.liaskovitis

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


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [PATCH v2] mm/hotplug: Verify hotplug memory range
  2013-08-10 19:17 [PATCH v2] mm/hotplug: Verify hotplug memory range Toshi Kani
       [not found] ` <20130811233722.GA27223@hacker.(null)>
@ 2013-08-14 22:09 ` Andrew Morton
  2013-08-14 23:34   ` Toshi Kani
  1 sibling, 1 reply; 6+ messages in thread
From: Andrew Morton @ 2013-08-14 22:09 UTC (permalink / raw)
  To: Toshi Kani
  Cc: linux-mm, linux-kernel, kosaki.motohiro, kamezawa.hiroyu, dave,
	isimatu.yasuaki, tangchen, vasilis.liaskovitis

On Sat, 10 Aug 2013 13:17:32 -0600 Toshi Kani <toshi.kani@hp.com> 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.
> 
> ...
>
> --- 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("Section-unaligned hotplug range: start 0x%llx, size 0x%llx\n",
> +				start, size);

Printing a u64 is problematic.  Here you assume that u64 is implemented
as unsigned long long.  But it can be implemented as unsigned long, by
architectures which use include/asm-generic/int-l64.h.  Such an
architecture will generate a compile warning here, but I can't
immediately find a Kconfig combination which will make that happen.

> +		return -EINVAL;
> +	}
> +
> +	return 0;
> +}


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [PATCH v2] mm/hotplug: Verify hotplug memory range
  2013-08-14 22:09 ` Andrew Morton
@ 2013-08-14 23:34   ` Toshi Kani
  2013-08-14 23:45     ` Andrew Morton
  0 siblings, 1 reply; 6+ messages in thread
From: Toshi Kani @ 2013-08-14 23:34 UTC (permalink / raw)
  To: Andrew Morton
  Cc: linux-mm, linux-kernel, kosaki.motohiro, kamezawa.hiroyu, dave,
	isimatu.yasuaki, tangchen, vasilis.liaskovitis

On Wed, 2013-08-14 at 15:09 -0700, Andrew Morton wrote:
> On Sat, 10 Aug 2013 13:17:32 -0600 Toshi Kani <toshi.kani@hp.com> 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.
> > 
> > ...
> >
> > --- 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("Section-unaligned hotplug range: start 0x%llx, size 0x%llx\n",
> > +				start, size);
> 
> Printing a u64 is problematic.  Here you assume that u64 is implemented
> as unsigned long long.  But it can be implemented as unsigned long, by
> architectures which use include/asm-generic/int-l64.h.  Such an
> architecture will generate a compile warning here, but I can't
> immediately find a Kconfig combination which will make that happen.

Oh, I see.  Should I add the casting below and resend it to you?

                (unsigned long long)start, (unsigned long long)size);

Thanks,
-Toshi


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [PATCH v2] mm/hotplug: Verify hotplug memory range
  2013-08-14 23:34   ` Toshi Kani
@ 2013-08-14 23:45     ` Andrew Morton
  2013-08-14 23:45       ` Toshi Kani
  0 siblings, 1 reply; 6+ messages in thread
From: Andrew Morton @ 2013-08-14 23:45 UTC (permalink / raw)
  To: Toshi Kani
  Cc: linux-mm, linux-kernel, kosaki.motohiro, kamezawa.hiroyu, dave,
	isimatu.yasuaki, tangchen, vasilis.liaskovitis

On Wed, 14 Aug 2013 17:34:02 -0600 Toshi Kani <toshi.kani@hp.com> wrote:

> > Printing a u64 is problematic.  Here you assume that u64 is implemented
> > as unsigned long long.  But it can be implemented as unsigned long, by
> > architectures which use include/asm-generic/int-l64.h.  Such an
> > architecture will generate a compile warning here, but I can't
> > immediately find a Kconfig combination which will make that happen.
> 
> Oh, I see.  Should I add the casting below and resend it to you?
> 
>                 (unsigned long long)start, (unsigned long long)size);

I was going to leave it as-is and see if anyone else can find a way of
triggering the warning.  But other sites in mm/memory_hotplug.c have
the casts so I went ahead and fixed it.


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [PATCH v2] mm/hotplug: Verify hotplug memory range
  2013-08-14 23:45     ` Andrew Morton
@ 2013-08-14 23:45       ` Toshi Kani
  0 siblings, 0 replies; 6+ messages in thread
From: Toshi Kani @ 2013-08-14 23:45 UTC (permalink / raw)
  To: Andrew Morton
  Cc: linux-mm, linux-kernel, kosaki.motohiro, kamezawa.hiroyu, dave,
	isimatu.yasuaki, tangchen, vasilis.liaskovitis

On Wed, 2013-08-14 at 16:45 -0700, Andrew Morton wrote:
> On Wed, 14 Aug 2013 17:34:02 -0600 Toshi Kani <toshi.kani@hp.com> wrote:
> 
> > > Printing a u64 is problematic.  Here you assume that u64 is implemented
> > > as unsigned long long.  But it can be implemented as unsigned long, by
> > > architectures which use include/asm-generic/int-l64.h.  Such an
> > > architecture will generate a compile warning here, but I can't
> > > immediately find a Kconfig combination which will make that happen.
> > 
> > Oh, I see.  Should I add the casting below and resend it to you?
> > 
> >                 (unsigned long long)start, (unsigned long long)size);
> 
> I was going to leave it as-is and see if anyone else can find a way of
> triggering the warning.  But other sites in mm/memory_hotplug.c have
> the casts so I went ahead and fixed it.

Thanks!
-Toshi



^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2013-08-14 23:47 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-08-10 19:17 [PATCH v2] mm/hotplug: Verify hotplug memory range Toshi Kani
     [not found] ` <20130811233722.GA27223@hacker.(null)>
2013-08-12 14:49   ` Toshi Kani
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

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