From: DX Cui <rijcos@gmail.com>
To: Dave Hansen <dave.hansen@intel.com>
Cc: linux-mm@kvack.org,
Matt Tolentino <matthew.e.tolentino@intel.com>,
Dave Hansen <haveblue@us.ibm.com>, Andrew Morton <akpm@osdl.org>,
Linus Torvalds <torvalds@osdl.org>,
Nathan Fontenot <nfont@linux.vnet.ibm.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: memory hot-add: the kernel can notify udev daemon before creating the sys file state?
Date: Thu, 29 May 2014 16:48:22 +0800 [thread overview]
Message-ID: <CAJm7N87BNiuNkqrU+EeeejXXp_aOH+jVh-kyZr890Aedg__Ftg@mail.gmail.com> (raw)
In-Reply-To: <53864B65.8080705@intel.com>
On Thu, May 29, 2014 at 4:47 AM, Dave Hansen <dave.hansen@intel.com> wrote:
> On 05/23/2014 05:27 AM, DX Cui wrote:
>> It looks the new "register_memory() --> ... -> device_add()" path has the
>> correct order for sysfs creation and notification udev.
>>
>> It would be great if you can confirm my analysis. :-)
>
> Your analysis looks correct to me. Nathan's patch does, indeed look
> like a quite acceptable fix. How far back do those sysfs attribute
> groups go, btw?
I'm not familiar with it.
My gut feeling is: this may need non-trivial efforts -- probably several
extra patches need to be backported too.
BTW, this race condition finally can cause kernel panic when old Linux
VMs of kernel versions <3.9.x, like CentOS 6.5, run on Hyper-V, AND
memory hot-add and the balloon driver are used:
https://bugzilla.redhat.com/show_bug.cgi?id=1102551
(there is a workaround patch for ***CentOS6.5*** in the bug entry)
-- DX
--
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>
prev parent reply other threads:[~2014-05-29 8:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-23 9:46 DX Cui
2014-05-23 12:27 ` DX Cui
2014-05-25 15:41 ` DX Cui
2014-05-28 20:32 ` Nathan Fontenot
2014-05-28 20:47 ` Dave Hansen
2014-05-29 8:48 ` DX Cui [this message]
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=CAJm7N87BNiuNkqrU+EeeejXXp_aOH+jVh-kyZr890Aedg__Ftg@mail.gmail.com \
--to=rijcos@gmail.com \
--cc=akpm@osdl.org \
--cc=dave.hansen@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=haveblue@us.ibm.com \
--cc=linux-mm@kvack.org \
--cc=matthew.e.tolentino@intel.com \
--cc=nfont@linux.vnet.ibm.com \
--cc=torvalds@osdl.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