Re: Back to the future.

[Linus Torvalds <torvalds@linux-foundation.org>]

On Sat, 28 Apr 2007, Rafael J. Wysocki wrote:
>
> > And can you name a _single_ advantage of doing so?
> 
> Yes.  We have a lot less interdependencies to worry about during the whole
> operation.

That's not an advantage. That's why it has *sucked*.

Trying to freeze kernel threads has _caused_ problems. It has _added_ 
these interdependencies. It hasn't removed a single dependency at any 
time, it has just added new problems!

> 1) if the kernel threads are frozen, we know that they don't hold any locks
> that could interfere with the freezing of device drivers,
> 2) if they are frozen, we know, for example, that they won't call user mode
> helpers or do similar things,
> 3) if they are frozen, we know that they won't submit I/O to disks and
> potentially damage filesystems (suspend2 has much more problems with that
> than swsusp, but still.  And yes, there have been bug reports related to it,
> so it's not just my fantasy).

NONE of these are valid explanations at all. You're listing totally 
theoretical problems, and ignoring all the _real_ problems that trying to 
freeze kernel threads has _caused_.

If you want to control user-mode helpers, you do that - you do not freeze 
kernel threads!

And no, kernel threads do not submit IO to disks on their own. You just 
made that up. Yes, they can be involved in that whole disk submission 
thing, but in a good way - they can be required in order to make disk 
writing work!

The problem that suspend has had is that it's done everything totally the 
wrong way around. Do kernel threads do disk IO? Sure, if asked to do so. 
For example, kernel threads can be involved in md etc, but that's a *good* 
thing. The way to shut them up is not to freeze the threads, but to freeze 
the *disk*.

		Linus