From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/netuio Bug 1655] Kernel crash when hot-unplug igb_uio device while DPDK application is running
Date: Mon, 03 Feb 2025 04:31:31 +0000 [thread overview]
Message-ID: <bug-1655-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1095 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1655
Bug ID: 1655
Summary: Kernel crash when hot-unplug igb_uio device while DPDK
application is running
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: netuio
Assignee: dev@dpdk.org
Reporter: nandinipersad361@gmail.com
Target Milestone: ---
When device has been bound to igb_uio driver and application is running,
hot-unplugging the device may cause kernel crash.
Reason:
When device is hot-unplugged, igb_uio driver will be removed which will destroy
UIO resources. Later trying to access any UIO resource will cause kernel crash.
Resolution/Workaround:
If using DPDK for PCI HW hot-unplug, prefer to bind device with VFIO instead of
IGB_UIO.
Affected Environment/Platform:
ALL.
Driver/Module:
igb_uio module.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 2979 bytes --]
reply other threads:[~2025-02-03 4:31 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-1655-3@http.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.