Thread (1 message) 1 message, 1 author, 2008-01-10

Re: [PATCH] PM: Acquire device locks on suspend

From: Alan Stern <stern@rowland.harvard.edu>
Date: 2008-01-10 17:04:06

On Thu, 10 Jan 2008, Rafael J. Wysocki wrote:
quoted
quoted
quoted
quoted
quoted
Also, the kerneldoc for destroy_suspended_device() should contain an 
extra paragraph warning that the routine should never be called except 
within the scope of a system sleep transition.  In practice this means 
it has to be directly or indirectly invoked by a suspend or resume 
method.
Or by a CPU hotplug notifier (that will be the majority of cases, IMO).
In your patch the call is made in response to a CPU_UP_CANCELED_FROZEN
notification.  Isn't it true that this notification is issued only as
part of a system sleep transition?
Yes, it is.
So it counts as being indirectly invoked by a resume method.
Rather, by the resume core.  Technically, it's invoked by
enable_nonboot_cpus(), which is not a resume method literally.
Okay, then the routine should only be called directly or indirectly 
from a suspend or resume method or from the suspend or resume core.

Alan Stern
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help