Bug#544145: marked as done (libc6-i686 - Segfaults on amd64/xen)
Your message dated Sun, 21 Feb 2010 10:52:23 +0100
with message-id <20100221095222.GA2420@galadriel.inutil.org>
and subject line Re: [Xen-devel] Crash with paravirt-ops 2.6.31.6 kernel
has caused the Debian Bug report #544145,
regarding libc6-i686 - Segfaults on amd64/xen
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
544145: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=544145
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: libc6-i686 - Segfaults on amd64/xen
- From: Bastian Blank <waldi@debian.org>
- Date: Sat, 29 Aug 2009 09:14:40 +0200
- Message-id: <20090829071440.GA23356@wavehammer.waldi.eu.org>
Package: libc6-i686
Version: 2.9-25
Severity: important
The last upgrade of my i386 chroot pulled in libc6-i686. After that all
binaries started to segfault:
| [ 38.652407] sh[3131]: segfault at 0 ip (null) sp 00000000ffb9a138 error 14 in bash[8048000+be000]
| [ 236.958701] ls[3650]: segfault at af7f22000 ip 0000000af7f22000 sp 00000000ff992390 error 14
| [ 252.066863] ls[3651]: segfault at af7fde000 ip 0000000af7fde000 sp 00000000ff8745f0 error 14
A removal of libc6-i686 or disabling via /etc/ld.so.nohwcap got the
system into a usable state again.
The system uses a amd64 kernel and userland on Xen.
Bastian
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (x86_64)
Kernel: Linux 2.6.31-rc8-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash
Versions of packages libc6-i686 depends on:
ii libc6 2.9-25 GNU C Library: Shared libraries
libc6-i686 recommends no packages.
libc6-i686 suggests no packages.
--
It is more rational to sacrifice one life than six.
-- Spock, "The Galileo Seven", stardate 2822.3
--- End Message ---
--- Begin Message ---
- To: 544145-done@bugs.debian.org
- Subject: Re: [Xen-devel] Crash with paravirt-ops 2.6.31.6 kernel
- From: Moritz Muehlenhoff <jmm@inutil.org>
- Date: Sun, 21 Feb 2010 10:52:23 +0100
- Message-id: <20100221095222.GA2420@galadriel.inutil.org>
- In-reply-to: <4B0DA080.7030904@goop.org>
- References: <28846609.721258484676784.JavaMail.root@ifrit.dereferenced.org> <20091122095403.GA1496@wavehammer.waldi.eu.org> <1258989935.7590.52.camel@zakaz.uk.xensource.com> <4B0AC6FA0200007800021812@vpn.id2.novell.com> <1258994658.7590.80.camel@zakaz.uk.xensource.com> <4B0D13850200007800021FC6@vpn.id2.novell.com> <4B0DA080.7030904@goop.org>
Version: 2.6.32-3
On Wed, Nov 25, 2009 at 01:24:16PM -0800, Jeremy Fitzhardinge wrote:
> On 11/25/09 02:22, Jan Beulich wrote:
> > Okay, I think I spotted the relevant difference: 2.6.18 and forward ports
> > set VGCF_in_syscall only when returning from 64-bit system calls (through
> > ret_from_sys_call) - 32-bit syscalls (regardless of the entry path taken)
> > return through int_ret_from_sys_call. 32-bit guest kernels shouldn't be
> > affected by this, as compat mode returns from the hypervisor
> > (compat_restore_all_guest) always use iret.
> >
>
> I think dropping the VCGF_in_syscall flag is the simplest possible fix
> then. There doesn't seem to be a huge benefit to using sysret in this
> case. Does this look OK?
>
> J
>
> Subject: [PATCH] xen: use iret for return from 64b kernel to 32b usermode
The patch was merged in 2.6.32.2, marking as fixed.
Cheers,
Moritz
--- End Message ---
Reply to: