RE: [x86/xsaves] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000b00

[Yu, Fenghua]

> From: Wu, Fengguang
> Sent: Saturday, May 09, 2015 5:29 AM
> To: Hansen, Dave
> 0day kernel testing robot got the below dmesg and the first bad commit is
> 
> https://github.com/hansendc/linux.git github-mpx
> 
> commit 4d90fc49c73730c09d7afd515f9c4e08d30229bd
> [    1.096425] Kernel panic - not syncing: Attempted to kill init!
> exitcode=0x00000b00 

The issue has already been fixed in https://lkml.org/lkml/2015/5/8/737

The patch in this git tree missed the following part when ported
to this git tree. It's the same mistake as the other two warnings
generated from the same commit.

diff --git a/arch/x86/kernel/i387.c b/arch/x86/kernel/i387.c
index 00918327..8a7b96b 100644
--- a/arch/x86/kernel/i387.c
+++ b/arch/x86/kernel/i387.c
@@ -166,6 +166,7 @@ static void init_thread_xstate(void)
 		setup_clear_cpu_cap(X86_FEATURE_XSAVE);
 		setup_clear_cpu_cap(X86_FEATURE_XSAVEOPT);
 		xstate_size = sizeof(struct i387_soft_struct);
+		user_xstate_size = xstate_size;
 		return;
 	}
 
@@ -173,6 +174,8 @@ static void init_thread_xstate(void)
 		xstate_size = sizeof(struct i387_fxsave_struct);
 	else
 		xstate_size = sizeof(struct i387_fsave_struct);
+
+	user_xstate_size = xstate_size;
 }
 
 /*

Thanks.

-Fenghua

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/