From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Rybchenko Subject: Re: [PATCH v2 11/11] ethdev: fix port removal notification timing Date: Thu, 10 May 2018 14:17:11 +0300 Message-ID: <924a1489-a8c7-e84b-380b-69e5c1ec9713@solarflare.com> References: <20180509094337.26112-1-thomas@monjalon.net> <20180509224313.27289-1-thomas@monjalon.net> <20180509224313.27289-12-thomas@monjalon.net> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit Cc: Matan Azrad To: Thomas Monjalon , Return-path: Received: from dispatch1-us1.ppe-hosted.com (dispatch1-us1.ppe-hosted.com [148.163.129.52]) by dpdk.org (Postfix) with ESMTP id 8FCEC1B95E for ; Thu, 10 May 2018 13:17:20 +0200 (CEST) In-Reply-To: <20180509224313.27289-12-thomas@monjalon.net> Content-Language: en-GB 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 05/10/2018 01:43 AM, Thomas Monjalon wrote: > From: Matan Azrad > > When an ethdev port is released, a destroy event is triggered to notify > the users about the released port. > > A bit before the destroy event is triggered, the port becomes invalid > by changing its state to UNUSED and cleaning its data. Therefore, the > port is invalid for the destroy event callback process and the users > may get a wrong information of the port. > > Move the destroy event emitting to be called before the port > invalidation. > > Fixes: 133b54779aa1 ("ethdev: fix port data reset timing") > Fixes: 29aa41e36de7 ("ethdev: add notifications for probing and removal") > Cc: stable@dpdk.org > > Signed-off-by: Matan Azrad > Acked-by: Thomas Monjalon > Reviewed-by: Ferruh Yigit Reviewed-by: Andrew Rybchenko