Re: [uml-devel] starting an 32 bit x86 chroot uml image at a ahrdened Gentoo amd64 system fails

2015-03-15 Thread Toralf Förster
On 03/13/2015 03:31 PM, Richard Weinberger wrote: > And what about a regular "unhardened" host? > Does it work if you boot a random x86_64 livecd? tested with GRML - failed too. (And I switched the compiler to gcc-4.8.3-vanilla before and compiled the linux exe with it) And last but not least -

Re: [uml-devel] starting an 32 bit x86 chroot uml image at a ahrdened Gentoo amd64 system fails

2015-03-15 Thread Richard Weinberger
Am 15.03.2015 um 11:54 schrieb Toralf Förster: > On 03/13/2015 03:31 PM, Richard Weinberger wrote: >> And what about a regular "unhardened" host? >> Does it work if you boot a random x86_64 livecd? > > tested with GRML - failed too. > (And I switched the compiler to gcc-4.8.3-vanilla before and co

Re: [uml-devel] starting an 32 bit x86 chroot uml image at a ahrdened Gentoo amd64 system fails

2015-03-15 Thread Richard Weinberger
Am 15.03.2015 um 11:54 schrieb Toralf Förster: > On 03/13/2015 03:31 PM, Richard Weinberger wrote: >> And what about a regular "unhardened" host? >> Does it work if you boot a random x86_64 livecd? > > tested with GRML - failed too. BTW: In GRML you need to remount /dev/shm with exec. Did you? T

Re: [uml-devel] starting an 32 bit x86 chroot uml image at a ahrdened Gentoo amd64 system fails

2015-03-15 Thread Toralf Förster
On 03/15/2015 11:59 AM, Richard Weinberger wrote: > Wait a moment. So, the failing UML is a 32bits UML? > The .config you sent me is UML x86_64... Ah - double error on my side - sent you the wrong .config, the non-working .config was a 32bit however (origin of this thread was: no crash, but during

Re: [uml-devel] starting an 32 bit x86 chroot uml image at a ahrdened Gentoo amd64 system fails

2015-03-15 Thread Toralf Förster
On 03/15/2015 12:27 PM, Richard Weinberger wrote: found the culprit : CONFIG_MPENTIUMM=y works where CONFIG_MCORE2=y do not work I do have an i5: processor : 3 vendor_id : GenuineIntel cpu family : 6 model : 69 model name : Intel(R) Core(TM) i5-4300U CPU @ 1.90GH

Re: [uml-devel] starting an 32 bit x86 chroot uml image at a ahrdened Gentoo amd64 system fails

2015-03-15 Thread Richard Weinberger
Am 15.03.2015 um 13:07 schrieb Toralf Förster: > On 03/15/2015 12:27 PM, Richard Weinberger wrote: > > found the culprit : > CONFIG_MPENTIUMM=y works where CONFIG_MCORE2=y do not work > > > I do have an i5: I have to double check this. Maybe you hint an UML bug. > processor : 3 > vendor_

Re: [uml-devel] starting an 32 bit x86 chroot uml image at a ahrdened Gentoo amd64 system fails

2015-03-15 Thread Richard Weinberger
Am 15.03.2015 um 13:07 schrieb Toralf Förster: > On 03/15/2015 12:27 PM, Richard Weinberger wrote: > > found the culprit : > CONFIG_MPENTIUMM=y works where CONFIG_MCORE2=y do not work BTW: Just ran a x86 UML with CONFIG_MCORE2=y. Works perfectly fine. But I have a different CPU. Thanks, //richar

[uml-devel] [PATCH 29/32] um: copy_thread(): rename 'arg' argument to 'kthread_arg'

2015-03-15 Thread Alex Dowad
The 'arg' argument to copy_thread() is only ever used when forking a new kernel thread. Hence, rename it to 'kthread_arg' for clarity (and consistency with do_fork() and other arch-specific implementations of copy_thread()). Signed-off-by: Alex Dowad --- arch/um/kernel/process.c | 9 +++-- 1

Re: [uml-devel] starting an 32 bit x86 chroot uml image at a ahrdened Gentoo amd64 system fails

2015-03-15 Thread Toralf Förster
On 03/15/2015 03:36 PM, Richard Weinberger wrote: > BTW: Just ran a x86 UML with CONFIG_MCORE2=y. Works perfectly fine. The picture isn't clear. After twiddling with the kernel config I got a working .config with CORE2=y. This runs fine if compiled with vanilla gcc 4.8.3. Compiled with the def

Re: [uml-devel] starting an 32 bit x86 chroot uml image at a ahrdened Gentoo amd64 system fails

2015-03-15 Thread Richard Weinberger
Am 15.03.2015 um 17:51 schrieb Toralf Förster: > On 03/15/2015 03:36 PM, Richard Weinberger wrote: >> BTW: Just ran a x86 UML with CONFIG_MCORE2=y. Works perfectly fine. > > The picture isn't clear. > > After twiddling with the kernel config I got a working .config with CORE2=y. > This runs fin