From: zhong jiang <zhongjiang@huawei.com>
To: Andrey Ryabinin <aryabinin@virtuozzo.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, 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: Wed, 3 Aug 2016 13:53:10 +0800 [thread overview]
Message-ID: <57A186C6.9050301@huawei.com> (raw)
In-Reply-To: <57A078B1.6060408@virtuozzo.com>
On 2016/8/2 18:40, Andrey Ryabinin wrote:
>
> On 08/01/2016 10:54 PM, Andrew Morton wrote:
>> 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.
> Ahem... https://lkml.kernel.org/r/<20150130133552.580f73b97a9bd007979b5419@linux-foundation.org>
>
> Also
>
> commit 786a8959912eb94fc2381c2ae487a96ce55dabca
> kasan: disable memory hotplug
>
> Currently memory hotplug won't work with KASan. As we don't have shadow
> for hotplugged memory, kernel will crash on the first access to it. To
> make this work we will need to allocate shadow for new memory.
>
> At some future point proper memory hotplug support will be implemented.
> Until then, print a warning at startup and disable memory hot-add.
>
>
>
>> What's the problem and are there plans to fix it?
> Nobody complained, so I didn't bother to fix it.
> The fix for this should be simple, I'll look into this.
>
>>> therefore, it is necessary to add the condition
>>> to limit the memory_hotplug when KASAN enable.
>>>
> I don't understand why we need Kconfig dependency.
> Why is that better than runtime warn message?
The user rarely care about the runtime warn message when the
system is good running. In fact, They are confilct with each other.
For me, I know the reason. but I always forget to do so. As a result,
I test the memory hotplug fails again. so, I hope to add the explicit dependency.
Thanks
zhongjiang
>>> 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>
>
>
--
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:[~2016-08-03 5:57 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
2016-08-02 1:41 ` zhong jiang
2016-08-02 10:40 ` Andrey Ryabinin
2016-08-03 5:53 ` zhong jiang [this message]
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=57A186C6.9050301@huawei.com \
--to=zhongjiang@huawei.com \
--cc=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 \
/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