[lkml]   [2002]   [Feb]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: current->state after kmalloc
    In article <> you wrote:

    > set_current_state(TASK_INTERRUPTIBLE);
    > kmalloc(sizeof(struct x), GFP_KERNEL);

    > what is current->state after kmalloc ?

    undefined. If kmalloc slept and you survived (due to setting
    TASK_INTERRUPTIBLE that's not guaranteed) then it'll most likely be
    If you depend on this your kernel code is broken in that has subtle
    dependencies on unspecified behavior and will break whenever kmalloc changes
    internal behavior.

    Arjan van de Ven

    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: 2005-03-22 13:23    [W:0.021 / U:7.096 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site