Looks good, thanks Andrew. If it is simple for you to see the commit which caused this regression, can you include the hash in a "fixes: <hash>" as is described in the DPDK contributor guidelines?