Re: [PATCH 1/4] x86: Save return value from kernel_thread

2016-05-21 Thread Brian Gerst
On Sat, May 21, 2016 at 9:44 PM, Andy Lutomirski wrote: > On Sat, May 21, 2016 at 9:04 AM, Brian Gerst wrote: >> Kernel threads should always return zero on success after calling >> do_execve(). The >> two existing cases in the kernel (kernel_init() and >> call_usermodehelper_exec_async()) >>

Re: [PATCH 1/4] x86: Save return value from kernel_thread

2016-05-21 Thread Andy Lutomirski
On Sat, May 21, 2016 at 9:04 AM, Brian Gerst wrote: > Kernel threads should always return zero on success after calling > do_execve(). The > two existing cases in the kernel (kernel_init() and > call_usermodehelper_exec_async()) > correctly do this. Save a few bytes by storing EAX/RAX instead

[PATCH 1/4] x86: Save return value from kernel_thread

2016-05-21 Thread Brian Gerst
Kernel threads should always return zero on success after calling do_execve(). The two existing cases in the kernel (kernel_init() and call_usermodehelper_exec_async()) correctly do this. Save a few bytes by storing EAX/RAX instead of an immediate zero. Also fix the 64-bit case which should sa