lkml.org 
[lkml]   [2000]   [Feb]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: 2.2.15pre5: still very unstable

On Fri, 4 Feb 2000, Manfred Spraul wrote:

> There are 2 different problems:
>
> * callers of gfp()/kmalloc()/get_user() that call these functions with
> !TASK_RUNNING, but which will set the state to TASK_RUNNING _without_
> calling schedule() inbetween. For them, it doesn't really matter, we
> don't need to change them.
>
> E.g. sys_wait4(): it calls put_user(), then
> set_current_state(TASK_RUNNING), then it returns without calling
> schedule().

i've noticed and fixed these places long time ago in the lowlatency patch
series. There are a couple of other places that call uaccess.h functions
with ->state != RUNNING, and this was causing latency problems. (actually
i worked it around)

-- mingo


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:56    [W:0.090 / U:1.064 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site