From: Toshi Kani <toshi.kani@hp.com>
To: Tang Chen <tangchen@cn.fujitsu.com>
Cc: gregkh@linuxfoundation.org, akpm@linux-foundation.org,
tj@kernel.org, hpa@zytor.com, mingo@elte.hu,
laijs@cn.fujitsu.com, isimatu.yasuaki@jp.fujitsu.com,
hutao@cn.fujitsu.com, guz.fnst@cn.fujitsu.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH v2 1/2] mem-hotplug: Avoid illegal state prefixed with legal state when changing state of memory_block.
Date: Fri, 13 Jun 2014 08:59:57 -0600 [thread overview]
Message-ID: <1402671597.7963.15.camel@misato.fc.hp.com> (raw)
In-Reply-To: <1402027134-14423-2-git-send-email-tangchen@cn.fujitsu.com>
On Fri, 2014-06-06 at 11:58 +0800, Tang Chen wrote:
> We use the following command to online a memory_block:
>
> echo online|online_kernel|online_movable > /sys/devices/system/memory/memoryXXX/state
>
> But, if we do the following:
>
> echo online_fhsjkghfkd > /sys/devices/system/memory/memoryXXX/state
>
> the block will also be onlined.
>
> This is because the following code in store_mem_state() does not compare the whole string,
> but only the prefix of the string.
>
> store_mem_state()
> {
> ......
> 328 if (!strncmp(buf, "online_kernel", min_t(int, count, 13)))
>
> Here, only compare the first 13 letters of the string. If we give "online_kernelXXXXXX",
> it will be recognized as online_kernel, which is incorrect.
>
> 329 online_type = ONLINE_KERNEL;
> 330 else if (!strncmp(buf, "online_movable", min_t(int, count, 14)))
>
> We have the same problem here,
>
> 331 online_type = ONLINE_MOVABLE;
> 332 else if (!strncmp(buf, "online", min_t(int, count, 6)))
>
> here,
>
> (Here is more problematic. If we give online_movalbe, which is a typo of online_movable,
> it will be recognized as online without noticing the author.)
>
> 333 online_type = ONLINE_KEEP;
> 334 else if (!strncmp(buf, "offline", min_t(int, count, 7)))
>
> and here.
>
> 335 online_type = -1;
> 336 else {
> 337 ret = -EINVAL;
> 338 goto err;
> 339 }
> ......
> }
>
> This patch fix this problem by using sysfs_streq() to compare the whole string.
>
> Reported-by: Hu Tao <hutao@cn.fujitsu.com>
> Signed-off-by: Tang Chen <tangchen@cn.fujitsu.com>
Acked-by: Toshi Kani <toshi.kani@hp.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>
next prev parent reply other threads:[~2014-06-13 15:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-06 3:58 [PATCH v2 0/2] Fix for memory online/offline Tang Chen
2014-06-06 3:58 ` [PATCH v2 1/2] mem-hotplug: Avoid illegal state prefixed with legal state when changing state of memory_block Tang Chen
2014-06-13 14:59 ` Toshi Kani [this message]
2014-06-06 3:58 ` [PATCH v2 2/2] mem-hotplug: Introduce MMOP_OFFLINE to replace the hard coding -1 Tang Chen
2014-06-06 5:15 ` Hu Tao
2014-06-06 5:33 ` [PATCH v2 RESEND " Tang Chen
2014-06-12 7:48 ` Tang Chen
2014-06-13 15:01 ` 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=1402671597.7963.15.camel@misato.fc.hp.com \
--to=toshi.kani@hp.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=guz.fnst@cn.fujitsu.com \
--cc=hpa@zytor.com \
--cc=hutao@cn.fujitsu.com \
--cc=isimatu.yasuaki@jp.fujitsu.com \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=tangchen@cn.fujitsu.com \
--cc=tj@kernel.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