From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 1733] Clarification Requested: Port Down Behavior When Trust Mode is Disabled in IAVF Driver
Date: Fri, 27 Jun 2025 11:12:31 +0000 [thread overview]
Message-ID: <bug-1733-3@https.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1992 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1733
Bug ID: 1733
Summary: Clarification Requested: Port Down Behavior When Trust
Mode is Disabled in IAVF Driver
Product: DPDK
Version: 24.11
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: gownivalla.susmitha@wipro.com
Target Milestone: ---
Hello DPDK Community,
I am currently working with the Intel IAVF driver in a DPDK environment and
have observed that when trust mode is set to off on a Virtual Function (VF),
the corresponding port goes down.
Despite reviewing available documentation and recent DPDK commits, I have not
found any official references explaining whether this behavior is:
1. An intended feature related to security or resource management,
2. A known limitation or side effect when disabling trust mode, or
3. A bug that may be addressed in future releases.
Additionally, I have looked for changes or bug reports related to the function
iavf_dev_alarm_handler or port link state management triggered by trust mode
changes but could not find relevant details.
Could anyone from the community or the DPDK development team please clarify:
1. Is the port going down when trust mode is disabled a documented and
expected behavior? If so, is there an official reference or documentation
available?
2. Are there any workarounds or best practices recommended when using trust
mode in production environments?
3. If this is a known issue or bug, is there a timeline for a fix?
Any insights or pointers to relevant code changes, documentation, or
discussions would be greatly appreciated.
Thank you in advance for your help!
Regards,
Susmitha
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3885 bytes --]
reply other threads:[~2025-06-27 11:12 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=bug-1733-3@https.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@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).