From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id 7D94156A2 for ; Fri, 27 May 2016 05:45:03 +0200 (CEST) Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by orsmga103.jf.intel.com with ESMTP; 26 May 2016 20:45:02 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.26,371,1459839600"; d="scan'208";a="111363319" Received: from yliu-dev.sh.intel.com (HELO yliu-dev) ([10.239.67.162]) by fmsmga004.fm.intel.com with ESMTP; 26 May 2016 20:45:01 -0700 Date: Fri, 27 May 2016 11:47:00 +0800 From: Yuanhan Liu To: Christian Ehrhardt , Martinx - ????? Cc: "Traynor, Kevin" , "" , dev , "Liu, Yuanhan" Message-ID: <20160527034700.GB5641@yliu-dev.sh.intel.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Subject: Re: [dpdk-dev] Crashing OVS+DPDK at the host, from inside of a KVM Guest X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 May 2016 03:45:03 -0000 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 - ジェームズ > > Cc: ; dev > > 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