Re: [dpdk-dev] Crashing OVS+DPDK at the host, from inside of a KVM Guest

[Yuanhan Liu <yuanhan.liu@linux.intel.com>]

On Wed, May 25, 2016 at 01:53:07PM +0000, Traynor, Kevin wrote:
> 
> > -----Original Message-----
> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Christian
> > Ehrhardt
> > Sent: Wednesday, May 25, 2016 7:06 AM
> > To: Martinx - ジェームズ <thiagocmartinsc@gmail.com>
> > Cc: <dev@openvswitch.org> <dev@openvswitch.org>; dev <dev@dpdk.org>
> > Subject: Re: [dpdk-dev] Crashing OVS+DPDK at the host, from inside of
> > a KVM Guest
> > 
> > Hi,
> > ping ...
> > 
> > Later on I want to look at it again once we upgraded to more recent
> > releases of the software components involved, but those have to be
> > made
> > ready to use first :-/
> > 
> > But the description is good and I wonder if anybody else could
> > reproduce
> > this and/or would have a hint on where this might come from or already
> > existing related fixes.
> > 
> > I mean in general nothing should be able to crash the host right?
> 
> Hi, I don't know if they are related to the issue that is being seen,
> but Yuanhan made some fixes in DPDK 16.04 regarding a malicious guest
> affecting the host. rte_vhost_dequeue_burst() is showing in the stack
> trace so it might worth testing with the latest code to see if it's the
> same issue and has been fixed.

Hi,

Try backporting following 3 patches? It might/should fix your issues:

    a436f53 vhost: avoid dead loop chain
    c687b0b vhost: check for ring descriptors overflow
    623bc47 vhost: do sanity check for ring descriptor length

Note that it will not apply cleanly on top of v2.2, but it should
trivial to do backport, as they are simple changes.


	--yliu