| commit | 11ebe4a3a51c597583df02572f6ddca844b6ecc8 | |
| author | Alok Kataria <akataria@vmware.com> | |
| Tue, 4 Aug 2009 22:34:22 +0000 (4 15:34 -0700) | ||
| committer | Greg Kroah-Hartman <gregkh@suse.de> | |
| Sun, 16 Aug 2009 21:19:07 +0000 (16 14:19 -0700) | ||
| tree | 602b534c6790a8bec403f42b1adb3f272b970288 | treesnapshot (tar.gz zip) |
| parent | fe1bbf0945bfff8913fe36b54bde71ebc412ce4b | commitdiff |
x86: Fix VMI && stack protector
commit 7d5b005652bc5ae3e1e0efc53fd0e25a643ec506 upstream.
With CONFIG_STACK_PROTECTOR turned on, VMI doesn't boot with
more than one processor. The problem is with the gs value not
being initialized correctly when registering the secondary
processor for VMI's case.
The patch below initializes the gs value for the AP to
__KERNEL_STACK_CANARY. Without this the secondary processor
keeps on taking a GP on every gs access.
Signed-off-by: Alok N Kataria <akataria@vmware.com>
LKML-Reference: <1249425262.18955.40.camel@ank32.eng.vmware.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
commit 7d5b005652bc5ae3e1e0efc53fd0e25a643ec506 upstream.
With CONFIG_STACK_PROTECTOR turned on, VMI doesn't boot with
more than one processor. The problem is with the gs value not
being initialized correctly when registering the secondary
processor for VMI's case.
The patch below initializes the gs value for the AP to
__KERNEL_STACK_CANARY. Without this the secondary processor
keeps on taking a GP on every gs access.
Signed-off-by: Alok N Kataria <akataria@vmware.com>
LKML-Reference: <1249425262.18955.40.camel@ank32.eng.vmware.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
| arch/x86/kernel/vmi_32.c | diffblobblamehistory |