From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:55843) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UwX00-00061l-9N for qemu-devel@nongnu.org; Tue, 09 Jul 2013 08:26:29 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UwWzy-00034z-2x for qemu-devel@nongnu.org; Tue, 09 Jul 2013 08:26:28 -0400 Received: from mx1.redhat.com ([209.132.183.28]:12351) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UwWzx-00034r-PF for qemu-devel@nongnu.org; Tue, 09 Jul 2013 08:26:25 -0400 Message-ID: <51DC016E.9070900@redhat.com> Date: Tue, 09 Jul 2013 08:26:22 -0400 From: Cole Robinson MIME-Version: 1.0 References: In-Reply-To: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] sending SEGV to qemu crashes host kernel in Fedora 19 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Dave Airlie Cc: qemu-devel@nongnu.org, LKML On 07/08/2013 09:11 PM, Dave Airlie wrote: > On Tue, Jul 9, 2013 at 10:35 AM, Dave Airlie wrote: >> Hi, >> >> F19 >> kernel-3.9.8-300.fc19.x86_64 >> qemu-kvm-1.4.2-4.fc19.x86_64 >> >> If I start a complete F19 install in the guest and send the qemu >> process a SEGV signal, the host kernel starts giving me random kmalloc >> errors soon after, if I send a normal kill signal things seem fine. >> >> CPU is Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz, on a HP 220z workstation. >> >> I initially blamed bad RAM but this reproduces everytime, and I >> swapped DIMMs around >> >> I haven't tested with upstream kernel/qemu yet, but I wondered if >> anyone else has seen this. >> >> I noticed this because some work I was doing was segfaulting my qemu >> and then my machine would die a few mins later. > > Of course now I read my fedora kernel emails and notice vhost_net does > bad things, > > disabling vhost_net seems to make it work fine, hopefully the next > Fedora kernel will bring the magic fixes. > That issue and another nasty crasher are being tracked here: https://bugzilla.redhat.com/show_bug.cgi?id=980254 - Cole