From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ferruh Yigit Subject: Re: [PATCH v2 0/6] net/tap: fixes and cleanups Date: Mon, 14 Jan 2019 14:10:25 +0000 Message-ID: References: <20190111180659.5972-1-stephen@networkplumber.org> <20190111203520.19944-1-stephen@networkplumber.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: dev@dpdk.org To: Stephen Hemminger , keith.wiles@intel.com Return-path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id 022581B295 for ; Mon, 14 Jan 2019 15:10:27 +0100 (CET) In-Reply-To: <20190111203520.19944-1-stephen@networkplumber.org> Content-Language: en-US List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On 1/11/2019 8:35 PM, Stephen Hemminger wrote: > The tap device (used by vdev_netvsc on Azure) has a bug that > prevents it working with primary/secondary process model because > the device name generation assumed a single process. The fix for > this is to have the kernel assign the device name (patch #5). > > While investigating this, found a number of other small issues > that should be cleaned up as well. > > v2 > - encorporate Keith's style feedback and ack > - use strlcpy instead of snprintf when copying "dtap%d" > since it makes intent clearer > - add another message cleanup > > Stephen Hemminger (7): > net/tap: use strlcpy for interface name > net/tap: allow full length names > net/tap: check interface name in kvargs > net/tap: lower the priority of log messages > net/tap: let kernel choose tun device name > net/tap: get rid of global tuntap_name > net/tap: don't print pointer in info message Series applied to dpdk-next-net/master, thanks.