lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 6 Dec 2011 16:04:56 -0800
From:	"Yu, Fenghua" <>
To:	Ingo Molnar <>, Borislav Petkov <>
CC:	"Srivatsa S. Bhat" <>,
	"Rafael J. Wysocki" <>,
	Thomas Gleixner <>,
	H Peter Anvin <>,
	Linus Torvalds <>,
	Andrew Morton <>,
	"Luck, Tony" <>,
	"Van De Ven, Arjan" <>,
	"Siddha, Suresh B" <>,
	"Brown, Len" <>,
	Randy Dunlap <>,
	Konrad Rzeszutek Wilk <>,
	Peter Zijlstra <>,
	linux-kernel <>,
	linux-pm <>, x86 <>,
	Tejun Heo <>,
	"Herrmann3, Andreas" <>
Subject: RE: [PATCH v4 0/7] x86: BSP or CPU0 online/offline

> The specific point i tried to make about s2ram is to make sure
> it does not break during normal usage: for example someone
> offlines the boot CPU, but the box then gets suspended - that
> should not hang or crash.
This has been considered in the patch #7/7. There shouldn't be a problem here (in theory).

Suspend/hibernate calls callback bsp_pm_callback() and must pass this check before it can continue.

When CPU0 is offline, bsp_pm_callback() returns -ENODEV and suspend/hibernate fails. When CPU0 is online, bsp_pm_callback() returns 0 and suspend/hibernate can continue.

So when CPU0 is offline, system cannot suspend/hibernate. Suspend/hibernate can succeed only when CPU0 is online.

Plus the patch #7/7 considers race condition by pm_notifier_call_chain()'s priority in pm call chain. So there should be race issue here.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists