DPDK usage discussions
 help / color / mirror / Atom feed
From: Srinivas Assampally <Srinivas.Assampally@tatacommunications.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: Malicious Driver Detection event
Date: Tue, 20 Sep 2022 06:50:15 +0000	[thread overview]
Message-ID: <TY0PR04MB624093F95821AD1E6B97D1EB864C9@TY0PR04MB6240.apcprd04.prod.outlook.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 571 bytes --]

Hi,

I'm facing the below error while running our DPDK-based application.

i40e_dev_alarm_handler(): ICR0: malicious programming detected
i40e_handle_mdd_event(): Malicious Driver Detection event 0x02 on TX queue 8 PF number 0x02 VF number 0x00 device 0000:3b:00.2

I'm having 20 Rx queues and 8 Tx queues and a 4-port LACP configuration.

The issue seems to have arisen after adding the ip-reassembly library for fragmented packets, especially after adding the logic of capturing sample packets before they Tx'ed.

Thanks in advance for your help,
Srini.


[-- Attachment #2: Type: text/html, Size: 2835 bytes --]

                 reply	other threads:[~2022-09-20  6:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=TY0PR04MB624093F95821AD1E6B97D1EB864C9@TY0PR04MB6240.apcprd04.prod.outlook.com \
    --to=srinivas.assampally@tatacommunications.com \
    --cc=users@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).