From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ferruh Yigit Subject: Re: [dpdk-stable] [PATCH 2/2] net/mlx5: fix probe failure report Date: Fri, 1 Sep 2017 11:40:47 +0100 Message-ID: <24ffbe60-ad35-7096-6675-9dcfdd2fb515@intel.com> References: <1502627112-53405-1-git-send-email-matan@mellanox.com> <1502627112-53405-2-git-send-email-matan@mellanox.com> <20170823094413.GT12995@autoinstall.dev.6wind.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Cc: Adrien Mazarguil , dev@dpdk.org, stable@dpdk.org To: =?UTF-8?Q?N=c3=a9lio_Laranjeiro?= , Matan Azrad Return-path: In-Reply-To: <20170823094413.GT12995@autoinstall.dev.6wind.com> 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 8/23/2017 10:44 AM, Nélio Laranjeiro wrote: > On Sun, Aug 13, 2017 at 03:25:12PM +0300, Matan Azrad wrote: >> The corrupted code doesn't return error when probe function >> fails due to error in device mac address getting. >> By this way, the probe function may return success even if the >> ETH dev is not allocated. >> >> Hence, the probe caller, for example failsafe PMD, fails when it >> tries to get ETH dev after the device was plugged out while mlx5 >> was probing it. >> >> The fix adds error report to the probe caller when priv_get_mac fails >> and in all other failure options which are missing it. >> >> By this way, it prevents the unexpected behavior to miss ETH device >> after the device was probed successfully. >> >> This bug was already present in the original code taken from mlx4. >> >> Fixes: 771fa900b73a ("mlx5: introduce new driver for Mellanox ConnectX-4 adapters") >> Fixes: 1371f4df16bc ("mlx5: check port is configured as ethernet device") >> >> Signed-off-by: Matan Azrad >> Cc: stable@dpdk.org > > Acked-by: Nelio Laranjeiro Applied to dpdk-next-net/master, thanks.