[lkml]   [2007]   [May]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 1/7] Freezer: Read PF_BORROWED_MM in a nonracy way
I guess I should just shut up and listen to experts... ok, just my
0.02 roubles.

Again, I can't comment things like "we just should never touch kernel",
because I don't even remotely undestand the things which actually use
freezer. I can only talk about the current implementation of freezer.

On 05/11, Linus Torvalds wrote:
> So, here's a summary:
> - we should not take the lock inside the function, because taking it
> there is fundamentally wrong, and leaves all the *other* races in
> place.
> - if you actually want to solve the other races, the lock needs to be
> taken by the caller, in which case taking it in the callee is obviously
> (again) wrong.
> - or then, we accept that the race wasn't fixed AT ALL, and you add other
> code to _other_ places to handle the case where you froze the wrong
> thread (or didn't freeze the right one).
> And I'm not making that up. Look at most of the other patches in that
> series: they are _exactly_ about the scenario I'm outlining.
> - the whole "kernel thread vs user thread" thing is the wrong thing to
> check in the first place, since we just should never touch kernel
> threads in the first place, and anything that wants to freeze user
> space should have disabled exec_usermodehelper() at a higher level
> That's why I'm so unhappy. The "fix" is going in the wrong direction. Each
> fix on their own may be an "improvement", but the end result of many of
> the fixes is a total mess!
> We can continue to add bandaids to something broken, until it "works". But
> the end result, while "working", is not actually any better. Quite the
> reverse - the end result of something like that is that you add all these
> magic rules and special cases.
> So in the end one ugly design decision leads to broken locking, which in
> turn leads to other cases where you add more broken code, which just leads
> to a situation where nobody actually understands what the *design* is,
> because there simply *isn't* any design - it's just a hodge-podge of "but
> this fixes a bug" ad-hoc "fixes".

Yes, the current design has many limitations. The major problem is that it
can't solve the dependencies: say T1 is frozen, and T2 can't be freezed
because it waits for T1. And I don't see how we can solve this problem
in general. And this is imho the source of most uglifications.

Let's look at the code. try_to_freeze_tasks() which can choose between
user/kernel threads is static. The exported freeze_processes() freeze
all of them. So why do we need is_user_space() at all? I am not sure
I know the right answer, but I think this was done to prevent the case
when user-space needs some kthread to make a progress and notice the
signal (TIF_FREEZE).

So yes, this is ugly, and is_user_space() is not reliable, and most
fixes are "let's fix this particular case", and each fix doesn't make
the code prettier.

But, on the other hand, the freezer is very simple and not intrusive.
When I first looked at the code 2 months ago, I thought we should do
something better. Since then, I have no ideas how to do this.


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

 \ /
  Last update: 2007-05-12 19:47    [W:0.091 / U:3.160 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site