Re: memory hot-add: the kernel can notify udev daemon before creating the sys file state?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, May 29, 2014 at 4:47 AM, Dave Hansen <dave.hansen@xxxxxxxxx> 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@xxxxxxxxx.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>




[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]