From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by dpdk.org (Postfix) with ESMTP id A134D2C15 for ; Fri, 22 Apr 2016 00:43:22 +0200 (CEST) Received: from orsmga002.jf.intel.com ([10.7.209.21]) by fmsmga101.fm.intel.com with ESMTP; 21 Apr 2016 15:43:16 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.24,514,1455004800"; d="scan'208";a="960148499" Received: from yliu-dev.sh.intel.com (HELO yliu-dev) ([10.239.67.162]) by orsmga002.jf.intel.com with ESMTP; 21 Apr 2016 15:43:14 -0700 Date: Thu, 21 Apr 2016 15:44:44 -0700 From: Yuanhan Liu To: Jianfeng Tan Cc: dev@dpdk.org, huawei.xie@intel.com Message-ID: <20160421224444.GC7603@yliu-dev.sh.intel.com> References: <1461242170-146337-1-git-send-email-jianfeng.tan@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1461242170-146337-1-git-send-email-jianfeng.tan@intel.com> User-Agent: Mutt/1.5.23 (2014-03-12) Subject: Re: [dpdk-dev] [PATCH] virtio: fix segfault when transmit pkts 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: Thu, 21 Apr 2016 22:43:23 -0000 On Thu, Apr 21, 2016 at 12:36:10PM +0000, Jianfeng Tan wrote: > Issue: when using virtio nic to transmit pkts, it causes segment fault. Jianfeng, It's good to describe the issues, steps to reproduce it and how to fix it. But you don't have to tell it like filling a form. Instead, you could try to describe in plain English. > How to reproduce: > a. start testpmd with vhost. > $testpmd -c 0x3 -n 4 --socket-mem 1024,0 --no-pci \ > --vdev 'eth_vhost0,iface=/tmp/sock0,queues=1' -- -i --nb-cores=1 I personally would suggest to add some indentations (and some whitespace lines), like a. start testpmd with vhost. $ testpmd -c 0x3 -n 4 ... \ --vdev '...' ... b. something else ... some more explanations. And, do not quote a command line like "$testpmd ...", it's like a var in base in this way. Instead, add a space after "$ ", like what I did above. > b. start a qemu with a virtio nic connected with the vhost-user port. This should be enough. I didn't find any special options below, therefore, above words is enough. However, if it's some specific option introduces a bug, you could claim it aloud then. > $qemu -smp cores=2,sockets=1 -cpu host -enable-kvm vm-0.img -vnc :5 -m 4G \ > -object memory-backend-file,id=mem,size=4096M,mem-path=,share=on \ > -numa node,memdev=mem -mem-prealloc \ > -chardev socket,id=char1,path=$sock_vhost \ > -netdev type=vhost-user,id=net1,chardev=char1 \ > -device virtio-net-pci,netdev=net1,mac=00:01:02:03:04:05 > c. enable testpmd on the host. > testpmd> set fwd io > testpmd> start > d. start testpmd in VM. > $testpmd -c 0x3 -n 4 -m 1024 -- -i --disable-hw-vlan-filter --txqflags=0xf01 > testpmd> set fwd txonly > testpmd> start > > How to fix: this bug is because inside virtqueue_enqueue_xmit(), the flag of > desc has been updated inside the do {} while (); and after the loop, all descs > could have run out, so idx is VQ_RING_DESC_CHAIN_END (32768), use this idx to > reference the start_dp array will lead to segment fault. You missed a fix line here. > Signed-off-by: Jianfeng Tan > --- > drivers/net/virtio/virtio_rxtx.c | 2 -- > 1 file changed, 2 deletions(-) > > diff --git a/drivers/net/virtio/virtio_rxtx.c b/drivers/net/virtio/virtio_rxtx.c > index ef21d8e..432aeab 100644 > --- a/drivers/net/virtio/virtio_rxtx.c > +++ b/drivers/net/virtio/virtio_rxtx.c > @@ -271,8 +271,6 @@ virtqueue_enqueue_xmit(struct virtqueue *txvq, struct rte_mbuf *cookie, > idx = start_dp[idx].next; > } while ((cookie = cookie->next) != NULL); > > - start_dp[idx].flags &= ~VRING_DESC_F_NEXT; This looks a good fix to me. I'm just wondering why we never met it before, and on which specific case do we meet it? Talking about that, seems like "set fwd txonly" is with high suspicious. --yliu