lkml.org 
[lkml]   [2002]   [Sep]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    Subjectproblem with "Use CLONE_KERNEL for the common kernel thread flags"?

    Seems to me like you missed something in your latest changeset:

    -#define CLONE_SIGNAL (CLONE_SIGHAND | CLONE_THREAD)
    +#define CLONE_KERNEL (CLONE_FS | CLONE_FILES | CLONE_SIGHAND)
    - kernel_thread(init, NULL, CLONE_FS | CLONE_FILES | CLONE_SIGNAL);
    + kernel_thread(init, NULL, CLONE_KERNEL);

    init used to be spawned with CLONE_THREAD and no longer is. Was this
    intentional? The changelog entry didn't indicate it, and I haven't
    been keeping track of what all the CLONE flags mean these days so I'm
    not sure if this is safe.

    --
    Revolutions do not require corporate support.
    -
    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: 2005-03-22 13:28    [W:4.118 / U:0.012 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site