From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ferruh Yigit Subject: Re: [dpdk-stable] [PATCH 11/11] ethdev: fix port removal notification timing Date: Wed, 9 May 2018 19:07:52 +0100 Message-ID: References: <20180509094337.26112-1-thomas@monjalon.net> <20180509094337.26112-12-thomas@monjalon.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: Matan Azrad , stable@dpdk.org To: Thomas Monjalon , dev@dpdk.org Return-path: In-Reply-To: <20180509094337.26112-12-thomas@monjalon.net> 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 5/9/2018 10: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