lkml.org 
[lkml]   [2007]   [Feb]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [RFC PATCH(Experimental) 0/4] Freezer based Cpu-hotplug
    On 02/18, Rafael J. Wysocki wrote:
    >
    > On Sunday, 18 February 2007 00:42, Oleg Nesterov wrote:
    > > On 02/17, Rafael J. Wysocki wrote:
    > > >
    > > > On Saturday, 17 February 2007 22:34, Oleg Nesterov wrote:
    > > > >
    > > > > static inline int is_user_space(struct task_struct *p)
    > > > > {
    > > > > return p->mm && !(p->flags & PF_BORROWED_MM);
    > > > > }
    > > > >
    > > > > This doesn't look right. First, an exiting task has ->mm == NULL after
    > > > > do_exit()->exit_mm(). Probably not a problem. However, PF_BORROWED_MM
    > > > > check is racy without task_lock(), so we can have a false positive as
    > > > > well. Is it ok? We can freeze aio_wq prematurely.
    > > >
    > > > Right now aio_wq is not freezeable (PF_NOFREEZE).
    > >
    > > Right now yes, but we are going to change this?
    >
    > Well, is there any more reliable (and not racy) method of differentiating
    > between kernel threads and user space processes?

    Not that I know of. At least, we can take task_lock() to really rule out
    kernel threads at FREEZER_USER_SPACE stage.

    Oleg.

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

    \
     
     \ /
      Last update: 2007-02-18 12:37    [W:3.430 / U:0.428 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site