From: Jeff Guo <jia.guo@intel.com>
To: marko.kovacevic@intel.com, john.mcnamara@intel.com,
qi.z.zhang@intel.com, ferruh.yigit@intel.com,
thomas@monjalon.net
Cc: dev@dpdk.org, jia.guo@intel.com, helin.zhang@intel.com,
konstantin.ananyev@intel.com, shaopeng.he@intel.com,
stephen@networkplumber.org, bruce.richardson@intel.com,
gaetan.rivet@6wind.com
Subject: [dpdk-dev] [PATCH] doc: add known igb_uio device hot-unplug issue
Date: Tue, 20 Nov 2018 23:09:31 +0800 [thread overview]
Message-ID: <1542726571-121934-1-git-send-email-jia.guo@intel.com> (raw)
When device has been bound to igb_uio driver and application is running,
hot-unplugging the device may cause kernel crash.
Signed-off-by: Jeff Guo <jia.guo@intel.com>
---
doc/guides/rel_notes/known_issues.rst | 21 +++++++++++++++++++++
1 file changed, 21 insertions(+)
diff --git a/doc/guides/rel_notes/known_issues.rst b/doc/guides/rel_notes/known_issues.rst
index 95e4ce6..dfe0565 100644
--- a/doc/guides/rel_notes/known_issues.rst
+++ b/doc/guides/rel_notes/known_issues.rst
@@ -759,3 +759,24 @@ Netvsc driver and application restart
**Driver/Module**:
``uio_hv_generic`` module.
+
+
+kernel crash when hot-unplug igb_uio device while DPDK application is running
+-----------------------------------------------------------------------------
+
+**Description**:
+ 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.
--
2.7.4
next reply other threads:[~2018-11-20 15:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-20 15:09 Jeff Guo [this message]
2018-11-20 18:02 ` Stephen Hemminger
2018-11-21 7:42 ` Jeff Guo
2018-11-22 17:46 ` Ferruh Yigit
2018-11-22 17:57 ` Mcnamara, John
2018-11-23 2:12 ` Thomas Monjalon
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=1542726571-121934-1-git-send-email-jia.guo@intel.com \
--to=jia.guo@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=gaetan.rivet@6wind.com \
--cc=helin.zhang@intel.com \
--cc=john.mcnamara@intel.com \
--cc=konstantin.ananyev@intel.com \
--cc=marko.kovacevic@intel.com \
--cc=qi.z.zhang@intel.com \
--cc=shaopeng.he@intel.com \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
/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).