Add support for OpenBSD
PATCH 3/3 Add support for OpenBSD
Hi!
This is the third and last patch.
This patch makes the xen kernel buildable on OpenBSD by adding support for ProPolice. ProPolice has been added to standard GCC in version 4.1.x under the name Stack Smashing Protection (SSP).
Cheers
Christoph
xen/arch/x86/boot/mkelf32.c +6 -0
@@ -90,9 +90,15 @@ static Elf32_Shdr out_shdr[] = { } }; +#ifndef swap16#define swap16 (_v) ((((u16)(_v)>>8)&0xff)|(((u16)(_v)&0xff)<<8)) +#endif +#ifndef swap32#define swap32 (_v) (((u32)swap16((u16)(_v))<<16)|(u32)swap16((u32)((_v)>>16))) +#endif +#ifndef swap64#define swap64 (_v) (((u64)swap32((u32)(_v))<<32)|(u64)swap32((u32)((_v)>>32))) +#endif static int big_endian;
xen/arch/x86/setup.c +3 -0
@@ -16,6 +16,7 @@#include <xen/percpu.h> #include <xen/hypercall.h> #include <xen/keyhandler.h> +#include <xen/guard.h> #include <public/version.h> #include <asm/bitops.h> #include <asm/smp.h>
@@ -625,6 +626,8 @@ void __init __start_xen(multiboot_info_t cmdline) != 0)panic ("Could not set up DOM0 guest OS\n" ); +init_guard (); +/* Scrub RAM that is still free and so may go to an unprivileged domain. */ scrub_heap_pages ();
xen/common/Makefile +1 -0
@@ -5,6 +5,7 @@ obj-y += elf.o obj-y += elf.o obj-y += event_channel.o obj-y += grant_table.o +obj-y += guard.o obj-y += kernel.o obj-y += keyhandler.o obj-y += lib.o
xen/common/guard.c new file +34 -0
@@ -0,0 +1,34 @@ + +#include <xen/lib.h> + +long __guard[8 ]; + +void __stack_smash_handler (char [],int __attribute__((unused))); + +void +__stack_smash_handler (char func[],int damaged) +{ +panic ("smashed stack in %s" , func); +} + + +void init_guard (void ) +{ +volatile long newguard[8 ]; +int i; + +/* XXX newguard is intended to get filled with random values. +* But there's nothing to use, so this is just something +* out of my head :) */ + newguard[0 ] =103958 ; + newguard[1 ] =3505 ; + newguard[2 ] =75601 ; + newguard[3 ] =35703 ; + newguard[4 ] =94 ; + newguard[5 ] =721 ; + newguard[6 ] =3094 ; + newguard[7 ] =217 ; + +for (i =sizeof (__guard) /sizeof (__guard[0 ]) -1 ; i; i--) + __guard[i] = newguard[i]; +}
xen/include/xen/guard.h new file +3 -0
@@ -0,0 +1,3 @@ + + +void init_guard (void );
+
_______________________________________________
Xen-devel mailing list
[email protected]
http://lists.xensource.com/xen-devel
Quoted 5 lines · Christoph Egger
This is the third and last patch.
This patch makes the xen kernel buildable on OpenBSD by adding support for ProPolice. ProPolice has been added to standard GCC in version 4.1.x under the name Stack Smashing Protection (SSP).
Gcc 4.1.x works fine for me already (under Linux at least). We specifically disable stack protection in xen/arch/x86/Rules.mk.
-- Keir
Quoted 9 lines · Keir Fraser
Quoted 5 lines · Christoph Egger
This is the third and last patch.
This patch makes the xen kernel buildable on OpenBSD by adding support for ProPolice. ProPolice has been added to standard GCC in version 4.1.x under the name Stack Smashing Protection (SSP).
Gcc 4.1.x works fine for me already (under Linux at least). We specifically disable stack protection in
xen/arch/x86/Rules.mk.
The stack protection is not just to improve security. With a stack protection, it is more likely that you find off-by-one bugs like this:
void foo(void)
{
char array[8];
int i;
for (i = 0; i <= 8; i++) {
array[i] = 0;
}
.....
}The propolice patch also contained a snippet, which necessary to make the Xen kernel build independ if SSP is disabled or not.
I extracted this snippet into a separate patch to fix this build error:
gcc -Wall -Werror -Wstrict-prototypes -O2 -fomit-frame-pointer -o boot/mkelf32 boot/mkelf32.cboot/mkelf32.c:93:1: "swap16" redefined
In file included from /usr/include/machine/endian.h:68,
from /usr/include/sys/types.h:45,
from /usr/include/stdio.h:45,
from boot/mkelf32.c:11:/usr/include/sys/endian.h:156:1: this is the location of the previous definitionboot/mkelf32.c:94:1: "swap32" redefined /usr/include/sys/endian.h:157:1: this is the location of the previous definitionboot/mkelf32.c:95:1: "swap64" redefined /usr/include/sys/endian.h:158:1: this is the location of the previous definition
gmake[2]: *** [boot/mkelf32] Error 1
This mail has two patches attached:
openbsd_buildfix.diff - the absolute necessary patch to make the kernel build on OpenBSD
openbsd_propolice.diff - it adds support for SSP
xen/arch/x86/boot/mkelf32.c +6 -0
@@ -90,9 +90,15 @@ static Elf32_Shdr out_shdr[] = { } }; +#ifndef swap16#define swap16 (_v) ((((u16)(_v)>>8)&0xff)|(((u16)(_v)&0xff)<<8)) +#endif +#ifndef swap32#define swap32 (_v) (((u32)swap16((u16)(_v))<<16)|(u32)swap16((u32)((_v)>>16))) +#endif +#ifndef swap64#define swap64 (_v) (((u64)swap32((u32)(_v))<<32)|(u64)swap32((u32)((_v)>>32))) +#endif static int big_endian;
xen/arch/x86/setup.c +3 -0
@@ -16,6 +16,7 @@#include <xen/percpu.h> #include <xen/hypercall.h> #include <xen/keyhandler.h> +#include <xen/guard.h> #include <public/version.h> #include <asm/bitops.h> #include <asm/smp.h>
@@ -668,6 +669,8 @@ void __init __start_xen(multiboot_info_t cmdline) != 0)panic ("Could not set up DOM0 guest OS\n" ); +init_guard (); +/* Scrub RAM that is still free and so may go to an unprivileged domain. */ scrub_heap_pages ();
xen/common/Makefile +1 -0
@@ -5,6 +5,7 @@ obj-y += elf.o obj-y += elf.o obj-y += event_channel.o obj-y += grant_table.o +obj-y += guard.o obj-y += kernel.o obj-y += keyhandler.o obj-y += lib.o
xen/common/guard.c new file +34 -0
@@ -0,0 +1,34 @@ + +#include <xen/lib.h> + +long __guard[8 ]; + +void __stack_smash_handler (char [],int __attribute__((unused))); + +void +__stack_smash_handler (char func[],int damaged) +{ +panic ("smashed stack in %s" , func); +} + + +void init_guard (void ) +{ +volatile long newguard[8 ]; +int i; + +/* XXX newguard is intended to get filled with random values. +* But there's nothing to use, so this is just something +* out of my head :) */ + newguard[0 ] =103958 ; + newguard[1 ] =3505 ; + newguard[2 ] =75601 ; + newguard[3 ] =35703 ; + newguard[4 ] =94 ; + newguard[5 ] =721 ; + newguard[6 ] =3094 ; + newguard[7 ] =217 ; + +for (i =sizeof (__guard) /sizeof (__guard[0 ]) -1 ; i; i--) + __guard[i] = newguard[i]; +}
xen/include/xen/guard.h new file +3 -0
@@ -0,0 +1,3 @@ + + +void init_guard (void );
_______________________________________________
Xen-devel mailing list
[email protected]
http://lists.xensource.com/xen-devel
Quoted 8 lines · Christoph Egger
/usr/include/sys/endian.h:156:1: this is the location of the previous definitionboot/mkelf32.c:94:1: "swap32" redefined/usr/include/sys/endian.h:157:1: this is the location of the previous definitionboot/mkelf32.c:95:1: "swap64" redefined/usr/include/sys/endian.h:158:1: this is the location of the previous definition
Is there a standard definition for these functions (i.e., can we be *sure* the original definitions have the same semantics as our own)? If not, which I think is the case, we're better off #undef'ing the old definitions.
-- Keir
Quoted 10 lines · Keir Fraser
Quoted 8 lines · Christoph Egger
/usr/include/sys/endian.h:156:1: this is the location of the previous definitionboot/mkelf32.c:94:1: "swap32" redefined/usr/include/sys/endian.h:157:1: this is the location of the previous definitionboot/mkelf32.c:95:1: "swap64" redefined/usr/include/sys/endian.h:158:1: this is the location of the previous definition
Quoted 3 lines
Is there a standard definition for these functions (i.e., can we be *sure* the original definitions have the same semantics as our own)? If not, which I think is the case, we're better off #undef'ing the old definitions.
This is the snippet of /usr/include/endian.h:
-----------------------------------------------------------------------------------
#ifdef __GNUC__
#define __swap16gen(x) __statement({ \
__uint16_t __swap16gen_x = (x); \
\
(__uint16_t)((__swap16gen_x & 0xff) << 8 | \
(__swap16gen_x & 0xff00) >> 8); \
})#define __swap32gen(x) __statement({ \
__uint32_t __swap32gen_x = (x); \
\
(__uint32_t)((__swap32gen_x & 0xff) << 24 | \
(__swap32gen_x & 0xff00) << 8 | \
(__swap32gen_x & 0xff0000) >> 8 | \
(__swap32gen_x & 0xff000000) >> 24); \
})#define __swap64gen(x) __statement({ \
__uint64_t __swap64gen_x = (x); \
\
(__uint64_t)((__swap64gen_x & 0xff) << 56 | \
(__swap64gen_x & 0xff00ULL) << 40 | \
(__swap64gen_x & 0xff0000ULL) << 24 | \
(__swap64gen_x & 0xff000000ULL) << 8 | \
(__swap64gen_x & 0xff00000000ULL) >> 8 | \
(__swap64gen_x & 0xff0000000000ULL) >> 24 | \
(__swap64gen_x & 0xff000000000000ULL) >> 40 | \
(__swap64gen_x & 0xff00000000000000ULL) >> 56); \
})#else /* __GNUC__ */
/* Note that these macros evaluate their arguments several times. */
#define __swap16gen(x) \
(__uint16_t)(((__uint16_t)(x) & 0xffU) << 8 | ((__uint16_t)(x) & 0xff00U) Quoted 1 line
Quoted 1 line
8)
#define __swap32gen(x) \
(__uint32_t)(((__uint32_t)(x) & 0xff) << 24 | \
((__uint32_t)(x) & 0xff00) << 8 | ((__uint32_t)(x) & 0xff0000) >> 8 |\
((__uint32_t)(x) & 0xff000000) >> 24)#define __swap64gen(x) \
(__uint64_t)((((__uint64_t)(x) & 0xff) << 56) | \
((__uint64_t)(x) & 0xff00ULL) << 40 | \
((__uint64_t)(x) & 0xff0000ULL) << 24 | \
((__uint64_t)(x) & 0xff000000ULL) << 8 | \
((__uint64_t)(x) & 0xff00000000ULL) >> 8 | \
((__uint64_t)(x) & 0xff0000000000ULL) >> 24 | \
((__uint64_t)(x) & 0xff000000000000ULL) >> 40 | \
((__uint64_t)(x) & 0xff00000000000000ULL) >> 56)#endif /* __GNUC__ */
-----------------------------------------------------------------------------------
Quoted 5 lines · Christoph Egger
Quoted 3 lines
Is there a standard definition for these functions (i.e., can we be *sure* the original definitions have the same semantics as our own)? If not, which I think is the case, we're better off #undef'ing the old definitions.
This is the snippet of
/usr/include/endian.h:
Well, that doesn't indicate whether the semantics of swap<16,32,etc> is standardised or not. I'll fix in mkelf32 by undef'ing.
-- Keir
Quoted 10 lines · Keir Fraser
Quoted 6 lines · Christoph Egger
Quoted 4 lines
Is there a standard definition for these functions (i.e., can we be *sure* the original definitions have the same semantics as our own)? If not, which I think is the case, we're better off #undef'ing the old definitions.
This is the snippet of
/usr/include/endian.h:Well, that doesn't indicate whether the semantics of swap<16,32,etc> is standardised or not. I'll fix in mkelf32 by undef'ing.
Thanks. I'm awaiting your commit. :-)