On Tue, Jun 15, 2021 at 12:32 PM Eric W. Biederman <ebiederm@xxxxxxxxxxxx> wrote: > > I had to update ret_from_kernel_thread to pop that state to get Linus's > change to boot. Apparently kernel_threads exiting needs to be handled. You are very right. That, btw, seems to be a horrible design mistake, but I think it's how "kernel_execve()" works - both for the initial "init", but also for user-mode helper processes. Both of those cases do "kernel_thread()" to create a new thread, and then that new kernel thread does kernel_execve() to create the user space image for that thread. And that act of "execve()" clears PF_KTHREAD from the thread, and then the final return from the kernel thread function returns to that new user space. Or something like that. It's been ages since I looked at that code, and your patch initially confused the heck out of me because I went "that can't _possibly_ be needed". But yes, I think your patch is right. And I think our horrible "kernel threads return to user space when done" is absolutely horrifically nasty. Maybe of the clever sort, but mostly of the historical horror sort. Or am I mis-rememberting how this ends up working? Did you look at exactly what it was that returned from kernel threads? This might be worth commenting on somewhere. But your patch for alpha looks correct to me. Did you have some test-case to verify ptrace() on io worker threads? Linus