Sean Christopherson ffac839d04 KVM: selftests: disable stack protector for all KVM tests ... Since 4.8.3, gcc has enabled -fstack-protector by default. This is problematic for the KVM selftests as they do not configure fs or gs segments (the stack canary is pulled from fs:0x28). With the default behavior, gcc will insert a stack canary on any function that creates buffers of 8 bytes or more. As a result, ucall() will hit a triple fault shutdown due to reading a bad fs segment when inserting its stack canary, i.e. every test fails with an unexpected SHUTDOWN. Fixes: 14c47b7530 ("kvm: selftests: introduce ucall") Signed-off-by: Sean Christopherson <sean.j.christopherson@intel.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>		2019-03-28 17:29:08 +01:00
..
fault-injection	License cleanup: add SPDX GPL-2.0 license identifier to files with no license	2017-11-02 11:10:55 +01:00
ktest	These commits have either been sitting in my INBOX or have been	2018-04-11 16:42:27 -07:00
nvdimm	device-dax for 5.1	2019-03-16 13:05:32 -07:00
radix-tree	radix tree: Don't return retry entries from lookup	2018-12-06 08:26:16 -05:00
scatterlist	tools/testing/scatterlist: Test new __sg_alloc_table_from_pages	2017-09-07 10:54:40 +01:00
selftests	KVM: selftests: disable stack protector for all KVM tests	2019-03-28 17:29:08 +01:00
vsock	VSOCK: add tools/testing/vsock/vsock_diag_test	2017-10-05 18:44:17 -07:00