* Description of problem:
When vhost-net is enabled as a backend on the RHEL6 KVM host, running netperf on the RHEL6 guest (again the host) will make the host panic. If
vhost-net is not loaded, with the same test, the issue doesn't occur.
( the attached rhel6-212-g1.xml is the libvirt XML for the guest,
dmesg.txt is the dmesg from the vmcore collected using kdump )
* Software Versions
a) On the RHEL6 host
b) Kernel version on the RHEL6 guest
c) netperf is from
* The issue is very easy to produce
* To produce
step 1) on the host
#> modprobe vhost-net
#> virsh start rhel6-212-g1
step 2) on the guest
#> netperf -H 192.168.122.1 -l 180 -t TCP_STREAM -c
Created attachment 423120 [details]
libvirt XML for the testing guest
Created attachment 423121 [details]
dmesg from the vmcore collected using kdump
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
*** Bug 603193 has been marked as a duplicate of this bug. ***
*** Bug 603293 has been marked as a duplicate of this bug. ***
Created attachment 424131 [details]
Revert "[net] bridge: make bridge support netpoll"
This patch reverts
Author: Amerigo Wang <firstname.lastname@example.org>
Date: Sat May 22 09:16:06 2010 -0400
[net] bridge: make bridge support netpoll
as it introduced a use-after-free bug on the bridge transmit path that affects all bridge users, regardless of whether netpoll is enabled or not.
*** Bug 604985 has been marked as a duplicate of this bug. ***
Patch(es) available on kernel-2.6.32-36.el6
Verified on kernel-2.6.32-37.el6 using steps mentioned in Comment 0, PASS.
Also tested according to https://bugzilla.redhat.com/show_bug.cgi?id=603293#c0, no kernel panic either.
set VERIFIED according to Comment 13
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.