On Thu, May 01, 2014 at 01:11:30PM -0400, Prarit Bhargava wrote:
[..]
diff --git a/98-kexec.rules b/98-kexec.rules
index 8c742dd..e32ee13 100644
--- a/98-kexec.rules
+++ b/98-kexec.rules
@@ -1,4 +1,4 @@
-SUBSYSTEM=="cpu", ACTION=="online", PROGRAM="/bin/systemctl
try-restart kdump.service"
-SUBSYSTEM=="cpu", ACTION=="offline", PROGRAM="/bin/systemctl
try-restart kdump.service"
-SUBSYSTEM=="memory", ACTION=="add", PROGRAM="/bin/systemctl
try-restart kdump.service"
-SUBSYSTEM=="memory", ACTION=="remove", PROGRAM="/bin/systemctl
try-restart kdump.service"
+SUBSYSTEM=="cpu", ACTION=="add", PROGRAM="/bin/systemctl
try-restart kdump.service"
+SUBSYSTEM=="cpu", ACTION=="remove", PROGRAM="/bin/systemctl
try-restart kdump.service"
So when is "add" event generated. After cpu has been added and that add
operation is complete?
IOW, I don't want a race between kexec-tools looking at
/sys/.../cpu<N>/crash_notes and cpu add operation. It should not happen
that cpu add operation is still in progress while kexec starts poking
in /sys. Otherwise potentially we can miss this cpu in /proc/vmcore.
Thanks
Vivek