On Mon, 2015-11-02 at 11:45 +0100, Jiri Kosina wrote: > > For example, if user space does a "read" or "write" on a character > device > > which is runtime-suspended at that point, the driver may want to > resume the > > device temporarily, carry out the operation and suspend it again, > but that > > generally won't work for the system suspend case. > > But why would this even be relevant in this discussion, given that at > the > point we are talking about, the whole userspace has been frozen > already? It really doesn't matter whether the thread in question is a kernel thread or user space. Device detection is even worse. Kernel threads that do either of these things must stop at defined points. You can use the freezer or go to another mechanism. I just doubt they'd act much different in the end. Regards Oliver -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
