• Al Viro's avatar
    infrastructure for saner ret_from_kernel_thread semantics · a74fb73c
    Al Viro authored
    * allow kernel_execve() leave the actual return to userland to
    caller (selected by CONFIG_GENERIC_KERNEL_EXECVE).  Callers
    updated accordingly.
    * architecture that does select GENERIC_KERNEL_EXECVE in its
    Kconfig should have its ret_from_kernel_thread() do this:
    	call schedule_tail
    	call the callback left for it by copy_thread(); if it ever
    returns, that's because it has just done successful kernel_execve()
    	jump to return from syscall
    IOW, its only difference from ret_from_fork() is that it does call the
    callback.
    * such an architecture should also get rid of ret_from_kernel_execve()
    and __ARCH_WANT_KERNEL_EXECVE
    
    This is the last part of infrastructure patches in that area - from
    that point on work on different architectures can live independently.
    Signed-off-by: default avatarAl Viro <viro@zeniv.linux.org.uk>
    a74fb73c
kmod.c 18.9 KB