linux-kernel - Re: KVM in -next is somewhat busted

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Mon, 08 Feb 2010 08:48:52 -0600
From:	Adam Litke <agl@...ibm.com>
To:	Avi Kivity <avi@...hat.com>
Cc:	Alan Cox <alan@...rguk.ukuu.org.uk>, linux-kernel@...r.kernel.org,
	KVM list <kvm@...r.kernel.org>,
	Rusty Russell <rusty@...tcorp.com.au>
Subject: Re: KVM in -next is somewhat busted

This is probably fixed by this patch from Rusty... Strangely, I have not
seen this on my test systems.

When running under qemu-kvm-0.11.0:

	BUG: unable to handle kernel paging request at 56e58955
	...
	Process vballoon (pid: 1297, ti=c7976000 task=c70a6ca0 task.ti=c7
	...
	Call Trace:
	 [<c88253a3>] ? balloon+0x1b3/0x440 [virtio_balloon]
	 [<c041c2d7>] ? schedule+0x327/0x9d0
	 [<c88251f0>] ? balloon+0x0/0x440 [virtio_balloon]
	 [<c014a2d4>] ? kthread+0x74/0x80
	 [<c014a260>] ? kthread+0x0/0x80
	 [<c0103b36>] ? kernel_thread_helper+0x6/0x30

need_stats_update should be zero-initialized.

Signed-off-by: Rusty Russell <rusty@...tcorp.com.au>
Cc: Adam Litke <agl@...ibm.com>

diff --git a/drivers/virtio/virtio_balloon.c b/drivers/virtio/virtio_balloon.c
--- a/drivers/virtio/virtio_balloon.c
+++ b/drivers/virtio/virtio_balloon.c
@@ -292,6 +292,7 @@ static int virtballoon_probe(struct virt
 	vb->num_pages = 0;
 	init_waitqueue_head(&vb->config_change);
 	vb->vdev = vdev;
+	vb->need_stats_update = 0;

 	/* We expect two virtqueues: inflate and deflate,
 	 * and optionally stat. */


On Mon, 2010-02-08 at 16:41 +0200, Avi Kivity wrote:
> (fixed kvm@ address)
> 
> 
> On 02/08/2010 04:27 PM, Alan Cox wrote:
> > Reliably at boot time with todays -next I get the following:
> >
> > BUG: unable to handle kernel paging request at 0000000000001028
> > IP: [<ffffffffa001c4c4>] balloon+0x1a1/0x309 [virtio_balloon]
> > PGD 2cd42067 PUD 3b9dc067 PMD 0
> > Oops: 0000 [#1] SMP
> > last sysfs file: /sys/devices/virtio-pci/virtio4/block/vdd/removable
> > CPU 3
> > Pid: 511, comm: vballoon Not tainted 2.6.33-rc7-next-20100208+ #51 /
> > RIP: 0010:[<ffffffffa001c4c4>]  [<ffffffffa001c4c4>] balloon+0x1a1/0x309 [virtio_balloon]
> >    
> 
> Looks like the guest is broken, not the host.  Do things work if you 
> leave out CONFIG_VIRTIO_BALLOON?
> 
> Copying Adam Litke, who's name is on the latest balloon changes.
> 


-- 
Thanks,
Adam

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/