On Tue, Dec 16, 2025 at 10:35:01AM +0000, Ciara Loftus wrote: > Depending on the underlying architecture and CPU flags available, a > different set of Rx/Tx paths may be defined by a driver using the common > path selection infrastructure. However the path selection function > iterates through the entire array of potential paths, regardless of > whether they are available for selection by that platform. This could > result in a null burst function being selected. Fix this by discarding > paths with a null burst function from selection. > > The fix for the Tx paths can be squashed into the next-net-intel tree > as the commit that it targets has not yet made it into the main branch. > > I added a third commit which addresses some minor inconsistencies in the > Rx path selection code and brings it in line with the Tx path selection > code. Functionally it remains the same. > > Ciara Loftus (3): > net/intel: prevent selection of a null Tx burst function > net/intel: prevent selection of a null Rx burst function > net/intel: bring common Rx path selection in line with Tx > Patch 1 squashed into original commit in net-net-intel. Other two applied as new commits in that tree.
Thanks, /Bruce
