On Wed, Oct 31, 2018 at 2:05 PM Saeed Mahameed [off-list ref] wrote:

Cong, How often does this happen ? can you some how verify if the
problematic packet has extra end padding after the ip payload ?

For us, we need 10+ hours to get one warning. This is also
why we never capture the packet that causes this warning.

It would be cool if we had a feature in kernel to store such SKB in
memory when such issue occurs, and let the user dump it later (via
tcpdump) and send the dump to the vendor for debug so we could just
replay and see what happens.

Yeah, the warning kinda sucks, it tells almost nothing, the SKB
should be dumped up on this warning.