[PATCH 8/9] ethdev: keep fast-path ops valid after port stop

Thomas Monjalon thomas at monjalon.net
Fri Jun 12 17:00:50 CEST 2026


11/06/2026 20:39, Maxime Leroy:
> Le jeu. 11 juin 2026, 18:01, Morten Brørup <mb at smartsharesystems.com> a
> écrit :
> 
> > > From: Maxime Leroy [mailto:maxime.leroys at gmail.com] On Behalf Of Maxime
> > > Leroy
> >
> > Good catch.
> > Acked-by: Morten Brørup <mb at smartsharesystems.com>
> >
> > Not related to the series, consider sending as separate patch.
> >
> Thanks for the review and Ack.
> 
> Agreed, this is a generic ethdev fix. I kept it in this series because the
> NAPI user depends on it.
> 
> The current Grout NAPI loop arms RX queue interrupts and then re-checks
> rte_eth_rx_queue_count() before blocking, to avoid sleeping when a packet
> arrived between the last empty poll and epoll_wait.
> 
> With the current ethdev reset path, rx_burst is replaced by a dummy
> callback on stop/release, but rx_queue_count becomes NULL. So if the port
> is stopped concurrently, the NAPI worker dereferences a NULL function
> pointer and
> segfaults on that recheck.
> 
> I can split it out if maintainers prefer, but then the dpaa2 NAPI series
> has a real dependency on the standalone ethdev fix.

You can keep this patch in the series AND
send it separately for a quick merge.




More information about the dev mailing list