[lkml]   [2003]   [Sep]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: call_usermodehelper does not report exit status?
    Andrew Morton <> wrote:
    > Omen Wild <Omen.Wild@Dartmouth.EDU> wrote:
    > >
    > > I found the call_usermodehelper function and
    > > call it with the wait flag set, but I cannot get a non-zero return
    > > status of the program to propagate into the kernel.
    > This might fix it.

    I think you missed the why behind the comment just above your first change.

    /* We don't have a SIGCHLD signal handler, so this
    * always returns -ECHILD, but the important thing is
    * that it blocks. */
    - sys_wait4(pid, NULL, 0, NULL);
    + sys_wait4(pid, &sub_info->retval, 0, NULL);

    The exit code notices that there is no signal handler for SIGCHILD and
    does a fast exit, then we notice when woken up the child no longer exists.

    Rusty discovered this back in June when we were trying to fix a checker
    error on the wait call, and decided that at the time no one was using the
    return value, hence the simpler fix.|src/|src/kernel|related/kernel/kmod.c

    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:48    [W:0.023 / U:30.128 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site