Hi! > > > 2) We can try to force uninterruptible tasks to get their "signals" anyway using > > > wake_up_state() directly on them (which I don't like as much). > > > > They are probably uninterruptible for a reason... > > > > If something is staying in UNINTERRUPTIBLE for more than 1 second, it > > is going to cause problems elsewhere, anyway. Do you see that happening? > > Probably. Please see, for example, this message sent to l-k: > > http://marc.theaimsgroup.com/?l=linux-kernel&m=111268969510393&w=2 ...hmm, perhaps kseriod needs suspend/resume support, or something; but that does not mean we should handle *all* uninterruptible tasks that way. > I can easily trigger a similar behavior with an uninterruptible task and I > have some problems with freezing tasks on SMP that smell like this too. > > If we are going to ignore uninterruptible tasks, I'd propose to set PF_FREEZE > and TIF_SIGPENDING for them without counting them as "todo" in You can't just ignore uninterruptible tasks, sorry. OTOH, if you want working refrigerator, Nigel has one ;-). We were talking about merging it to mainline few times already... Pavel -- People were complaining that M$ turns users into beta-testers... ...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
