search for: vsyscal

...2007-02-27/arch/i386/kernel/Makefile =================================================================== --- head-2007-02-27.orig/arch/i386/kernel/Makefile 2007-03-05 10:00:18.000000000 +0100 +++ head-2007-02-27/arch/i386/kernel/Makefile 2007-02-27 16:27:37.000000000 +0100 @@ -74,6 +74,52 @@ $(obj)/vsyscall-%.so: $(src)/vsyscall.ld $(obj)/vsyscall-%.o $(obj)/$(vsyscall_note) FORCE $(call if_changed,syscall) +ifeq ($(CONFIG_XEN)$(CONFIG_COMPAT_VDSO),yy) + +# vsyscall.o also contains the vsyscall DSO relocation info as __initdata. +# We must build both alternative images before we can asse...

...2007-02-27/arch/i386/kernel/Makefile =================================================================== --- head-2007-02-27.orig/arch/i386/kernel/Makefile 2007-03-05 10:00:18.000000000 +0100 +++ head-2007-02-27/arch/i386/kernel/Makefile 2007-02-27 16:27:37.000000000 +0100 @@ -74,6 +74,52 @@ $(obj)/vsyscall-%.so: $(src)/vsyscall.ld $(obj)/vsyscall-%.o $(obj)/$(vsyscall_note) FORCE $(call if_changed,syscall) +ifeq ($(CONFIG_XEN)$(CONFIG_COMPAT_VDSO),yy) + +# vsyscall.o also contains the vsyscall DSO relocation info as __initdata. +# We must build both alternative images before we can asse...

...2007-02-27/arch/i386/kernel/Makefile =================================================================== --- head-2007-02-27.orig/arch/i386/kernel/Makefile 2007-03-05 10:00:18.000000000 +0100 +++ head-2007-02-27/arch/i386/kernel/Makefile 2007-02-27 16:27:37.000000000 +0100 @@ -74,6 +74,52 @@ $(obj)/vsyscall-%.so: $(src)/vsyscall.ld $(obj)/vsyscall-%.o $(obj)/$(vsyscall_note) FORCE $(call if_changed,syscall) +ifeq ($(CONFIG_XEN)$(CONFIG_COMPAT_VDSO),yy) + +# vsyscall.o also contains the vsyscall DSO relocation info as __initdata. +# We must build both alternative images before we can asse...

AFAICT we'll pay one extra TLB entry for this patch. Zach had a patch which left the vsyscall page at the top of memory (minus hole for hypervisor) and patched the ELF header at boot. Thoughts welcome, Rusty. Name: Move vsyscall page out of fixmap, above stack Author: Gerd Hoffmann <kraxel@suse.de> Hypervisors want to use memory at the top of the address space (eg. 64MB for Xen, o...

AFAICT we'll pay one extra TLB entry for this patch. Zach had a patch which left the vsyscall page at the top of memory (minus hole for hypervisor) and patched the ELF header at boot. Thoughts welcome, Rusty. Name: Move vsyscall page out of fixmap, above stack Author: Gerd Hoffmann <kraxel@suse.de> Hypervisors want to use memory at the top of the address space (eg. 64MB for Xen, o...

Debian kernels have disabled legacy vsyscall page support meaning they cannot runs binaries that predate c.2013. To enable it again you must add vsyscall=emulate to the kernel command line when booting. It's unclear why Debian disabled this as according to the documentation: Disabling this option saves about 7K of kernel size and...

...pod index 251b4919f..09f505f91 100644 --- a/v2v/virt-v2v.pod +++ b/v2v/virt-v2v.pod @@ -977,6 +977,25 @@ A recommended procedure is, before using virt-v2v, to check that the boot kernel is the best kernel available in the guest (for example by making sure the guest is up-to-date). +=head2 "vsyscall attempted with vsyscall=none" + +When run on a recent Debian host virt-v2v may fail to convert guests +which were created before 2013. In the debugging output you will see +a crash message similar to: + + vsyscall attempted with vsyscall=none ip:... + segfault at ... + +This is caused becaus...

plain text document attachment (xx-paravirt-vsyscall.patch) vsyscall interface updates for paravirt ops. Signed-off-by: Steven Rostedt srostedt@redhat.com Signed-off-by: Glauber de Oliveira Costa <gcosta@redhat.com> Index: clean-start/arch/x86_64/kernel/vsyscall.c =================================================================== --- clean...

plain text document attachment (xx-paravirt-vsyscall.patch) vsyscall interface updates for paravirt ops. Signed-off-by: Steven Rostedt srostedt@redhat.com Signed-off-by: Glauber de Oliveira Costa <gcosta@redhat.com> Index: clean-start/arch/x86_64/kernel/vsyscall.c =================================================================== --- clean...

This fixes various problems that cropped up with the vdso patches. - Patch 1 fixes an information leak to userspace. - Patches 2 and 3 fix the kernel build on gold. - Patches 4 and 5 fix Xen (I hope). - Patch 6 (optional) adds a trace event to vsyscall emulation. It will make it easier to handle performance regression reports :) [1] https://gitorious.org/linux-test-utils/linux-clock-tests Changes from v1: - Improve changelog message for "x86-64/xen: Enable the vvar mapping" - Fix 32-bit build. - Add patch 6. Andy Lutomirski (...

This fixes various problems that cropped up with the vdso patches. - Patch 1 fixes an information leak to userspace. - Patches 2 and 3 fix the kernel build on gold. - Patches 4 and 5 fix Xen (I hope). - Patch 6 (optional) adds a trace event to vsyscall emulation. It will make it easier to handle performance regression reports :) [1] https://gitorious.org/linux-test-utils/linux-clock-tests Changes from v1: - Improve changelog message for "x86-64/xen: Enable the vvar mapping" - Fix 32-bit build. - Add patch 6. Andy Lutomirski (...

This fixes various problems that cropped up with the vdso patches. - Patch 1 fixes an information leak to userspace. - Patches 2 and 3 fix the kernel build on gold. - Patches 4 and 5 fix Xen (I hope). - Patch 6 (optional) adds a trace event to vsyscall emulation. It will make it easier to handle performance regression reports :) [1] https://gitorious.org/linux-test-utils/linux-clock-tests Changes from v1: - Improve changelog message for "x86-64/xen: Enable the vvar mapping" - Fix 32-bit build. - Add patch 6. Andy Lutomirski (...

...Torvalds <torvalds@osdl.org> To: Rusty Russell <rusty@rustcorp.com.au> Cc: Andrew Morton <akpm@osdl.org> Subject: Re: [Fwd: [Fwd: FW: argh]] Date: Wed, 17 May 2006 21:35:51 -0700 (PDT) On Thu, 18 May 2006, Rusty Russell wrote: > > PS. Linus, any feedback on the "move-vsyscall-into-user-address-range" > patch stolen from exec-shield? I'm not against it, but it needs tons of testing in -mm first. Since the vsyscall page has been at a fixed address, there might be real programs that hardcoded it etc. I'd also want sign-off from Gerd and Ingo, obviously...

...Torvalds <torvalds@osdl.org> To: Rusty Russell <rusty@rustcorp.com.au> Cc: Andrew Morton <akpm@osdl.org> Subject: Re: [Fwd: [Fwd: FW: argh]] Date: Wed, 17 May 2006 21:35:51 -0700 (PDT) On Thu, 18 May 2006, Rusty Russell wrote: > > PS. Linus, any feedback on the "move-vsyscall-into-user-address-range" > patch stolen from exec-shield? I'm not against it, but it needs tons of testing in -mm first. Since the vsyscall page has been at a fixed address, there might be real programs that hardcoded it etc. I'd also want sign-off from Gerd and Ingo, obviously...

This fixes various problems that cropped up with the vdso patches. - Patch 1 fixes an information leak to userspace. - Patches 2 and 3 fix the kernel build on gold. - Patches 4 and 5 fix Xen (I hope). Konrad, could you could test these on Xen and run 'test_vsyscall test' [1]? I don't have a usable Xen setup. Also, I'd appreciate a review of patches 4 and 5 from some Xen/paravirt people. [1] https://gitorious.org/linux-test-utils/linux-clock-tests Andy Lutomirski (5): x86-64: Pad vDSO to a page boundary x86-64: Move the "user" vs...

This fixes various problems that cropped up with the vdso patches. - Patch 1 fixes an information leak to userspace. - Patches 2 and 3 fix the kernel build on gold. - Patches 4 and 5 fix Xen (I hope). Konrad, could you could test these on Xen and run 'test_vsyscall test' [1]? I don't have a usable Xen setup. Also, I'd appreciate a review of patches 4 and 5 from some Xen/paravirt people. [1] https://gitorious.org/linux-test-utils/linux-clock-tests Andy Lutomirski (5): x86-64: Pad vDSO to a page boundary x86-64: Move the "user" vs...

This fixes various problems that cropped up with the vdso patches. - Patch 1 fixes an information leak to userspace. - Patches 2 and 3 fix the kernel build on gold. - Patches 4 and 5 fix Xen (I hope). Konrad, could you could test these on Xen and run 'test_vsyscall test' [1]? I don't have a usable Xen setup. Also, I'd appreciate a review of patches 4 and 5 from some Xen/paravirt people. [1] https://gitorious.org/linux-test-utils/linux-clock-tests Andy Lutomirski (5): x86-64: Pad vDSO to a page boundary x86-64: Move the "user" vs...

Hi, If the pristine centos:centos5 centos:centos6 images are not running on your brand new host running another linux distribution, you might be hitting this issue: https://github.com/CentOS/sig-cloud-instance-images/issues/62 https://bugs.alpinelinux.org/issues/6928 Cheers Tru -- Tru Huynh http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xBEFA581B -------------- next part

...oes not help there. This patch introduces a > new flag to automatically clear memory contents on VM suspend/resume, > which will allow random number generators to reseed when virtual > machines get cloned. Umm. If this is real problem, should kernel provide such rng in the vsdo page using vsyscalls? Kernel can have special interface to its vsyscalls, but we may not want to offer this functionality to rest of userland... > - Provides a simple mechanism to avoid RAM exfiltration during > traditional sleep/hibernate on a laptop or desktop when memory, > and thus secrets, are v...

...oes not help there. This patch introduces a > new flag to automatically clear memory contents on VM suspend/resume, > which will allow random number generators to reseed when virtual > machines get cloned. Umm. If this is real problem, should kernel provide such rng in the vsdo page using vsyscalls? Kernel can have special interface to its vsyscalls, but we may not want to offer this functionality to rest of userland... > - Provides a simple mechanism to avoid RAM exfiltration during > traditional sleep/hibernate on a laptop or desktop when memory, > and thus secrets, are v...