linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: zhongjiang <zhongjiang@huawei.com>
Cc: linux-mm@kvack.org, Andrey Ryabinin <aryabinin@virtuozzo.com>,
	Alexander Potapenko <glider@google.com>,
	Dmitry Vyukov <dvyukov@google.com>,
	kasan-dev@googlegroups.com
Subject: Re: [PATCH] mm: add restriction when memory_hotplug config enable
Date: Mon, 1 Aug 2016 12:54:17 -0700	[thread overview]
Message-ID: <20160801125417.ece9c623f03d952a60113a3f@linux-foundation.org> (raw)
In-Reply-To: <1470063651-29519-1-git-send-email-zhongjiang@huawei.com>

On Mon, 1 Aug 2016 23:00:51 +0800 zhongjiang <zhongjiang@huawei.com> wrote:

> From: zhong jiang <zhongjiang@huawei.com>
> 
> At present, It is obvious that memory online and offline will fail
> when KASAN enable,

huh, I didn't know that.  What's the problem and are there plans to fix it?

>  therefore, it is necessary to add the condition
> to limit the memory_hotplug when KASAN enable.
> 
> Signed-off-by: zhong jiang <zhongjiang@huawei.com>
> ---
>  mm/Kconfig | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/mm/Kconfig b/mm/Kconfig
> index 3e2daef..f6dd77e 100644
> --- a/mm/Kconfig
> +++ b/mm/Kconfig
> @@ -187,6 +187,7 @@ config MEMORY_HOTPLUG
>  	bool "Allow for memory hot-add"
>  	depends on SPARSEMEM || X86_64_ACPI_NUMA
>  	depends on ARCH_ENABLE_MEMORY_HOTPLUG
> +	depends on !KASAN
>  
>  config MEMORY_HOTPLUG_SPARSE
>  	def_bool y

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

  reply	other threads:[~2016-08-01 19:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-01 15:00 zhongjiang
2016-08-01 19:54 ` Andrew Morton [this message]
2016-08-02  1:41   ` zhong jiang
2016-08-02 10:40   ` Andrey Ryabinin
2016-08-03  5:53     ` zhong jiang
2016-08-04 20:08       ` Andrew Morton

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=20160801125417.ece9c623f03d952a60113a3f@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=aryabinin@virtuozzo.com \
    --cc=dvyukov@google.com \
    --cc=glider@google.com \
    --cc=kasan-dev@googlegroups.com \
    --cc=linux-mm@kvack.org \
    --cc=zhongjiang@huawei.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