Re: [PATCH V2] exit: trigger panic when global init has exited

Hi Eric,Oleg > As Oleg pointer out we need to do something like the code below. > > diff --git a/kernel/exit.c b/kernel/exit.c > index 04029e35e69a..bc676c06ef9a 100644 > --- a/kernel/exit.c > +++ b/kernel/exit.c > @@ -785,15 +785,16 @@ void __noreturn do_exit(long code) >

Re: [PATCH V2] exit: trigger panic when global init has exited

Qianli Zhao writes: > From: Qianli Zhao > > When init sub-threads running on different CPUs exit at the same time, > zap_pid_ns_processe()->BUG() may be happened. > And every thread status is abnormal after exit(PF_EXITING set,task->mm=NULL > etc), > which makes it difficult to parse coredump

Re: [PATCH V2] exit: trigger panic when global init has exited

On 03/12, Qianli Zhao wrote: > > --- a/kernel/exit.c > +++ b/kernel/exit.c > @@ -767,6 +767,17 @@ void __noreturn do_exit(long code) > validate_creds_for_do_exit(tsk); > > /* > + * If global init has exited, > + * panic immediately to get a useable coredump. > + */ > +

[PATCH V2] exit: trigger panic when global init has exited

From: Qianli Zhao When init sub-threads running on different CPUs exit at the same time, zap_pid_ns_processe()->BUG() may be happened. And every thread status is abnormal after exit(PF_EXITING set,task->mm=NULL etc), which makes it difficult to parse coredump from fulldump normally. In order to