Re: mbuf refcnt issue

[Stephen Hemminger <stephen@networkplumber.org>]

On Tue, 15 Apr 2025 13:10:18 +0000
"Lombardo, Ed" <Ed.Lombardo@netscout.com> wrote:

> Hi,
> I enabled more logging, and I see the following ICE Driver Malicious Driver Detection event 6 and 7, in the dpdk_log.txt when failure occurs.
> 
> EAL: Allocated 2112 bytes of per-lcore data with a 64-byte alignment
> ICE_INIT: ice_load_pkg_type(): Active package is: 1.3.35.0, ICE OS Default Package (single VLAN mode)
> ICE_INIT: ice_load_pkg_type(): Active package is: 1.3.35.0, ICE OS Default Package (single VLAN mode)
> MBUF: Registered dynamic field rte_dynfield_timestamp (sz=8, al=8, fl=0x0) -> 96
> MBUF: Registered dynamic flag rte_dynflag_rx_timestamp (fl=0x0) -> 23
> MBUF: Registered dynamic field rte_mbuf_dynfield_udata64 (sz=8, al=8, fl=0x0) -> 104
> ICE_DRIVER: ice_interrupt_handler(): OICR: MDD event
> ICE_DRIVER: ice_interrupt_handler(): Malicious Driver Detection event 7 by TCLAN on TX queue 2 PF# 0
> ICE_DRIVER: ice_interrupt_handler(): Malicious Driver Detection event 6 by TDPU on TX queue 2 PF# 0
> 
> Are malformed packets handled by DPDK, can malformed packets corrupt the mbufs?
> 
> Thanks,
> Ed

I do not know. The malicious driver detection is when application asks
to send a packet on a VF that is not for that VF. I.e source MAC or VLAN mismatch.