From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pl1-f195.google.com (mail-pl1-f195.google.com [209.85.214.195]) by dpdk.org (Postfix) with ESMTP id 63DCB2BD5 for ; Tue, 20 Nov 2018 19:02:22 +0100 (CET) Received: by mail-pl1-f195.google.com with SMTP id t13so1428043ply.13 for ; Tue, 20 Nov 2018 10:02:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=XoUiXoic3kUEPwAMUd/cM7UwRGesF3XPoibKFmqtcE0=; b=q7NcskgqB8yR5/QqahDYqn92k7J+hlSO12eqO0hLPTpNtqi1j91Eppb1CC2pY7Jk3Y FnWw4kMx60S7btSQ0C0lSi/+/JWAd+SjDEzVI0yGSx5duoXnu2pwumc57Y7Jz86EUm9T xCEvLKTzyNpECqfoZgtqpKUOMAnCDmy7QRnT/G6cNPDfLJSAYow3/cyP0vWCf4w22qPp ominMms7cLG1WfrTrk+yIWkAIuDJ/KNw0OLITRYUctCg4D4WAwXMVQcn/7fE/dILdpdt djivy4oGrtIA7xFHax9GrnyGvNEVXIIiOO438FusZsIkIKKbnlS+h3FDkS5Mxj9IddLC 2VgA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=XoUiXoic3kUEPwAMUd/cM7UwRGesF3XPoibKFmqtcE0=; b=qnuOqD9BZsxLgcphgBmKQGJKQh8eHCiWlf7wPy50RU1QrvyCI9a24nMh8a92thwFKX oDrcmLj3E2mXm8WdYegxlv3cdhP5maT2OrufELEL8Sa5jbNPX8Z6qugzgdu4sxS38i8t oPFSiRv2RNI/kwnw8Z+FJKlFQlGxHU8c+H5wXBg8IwKEr6H8xnMu/xJxk7nPPAl2tc+c pvesenIZNPxDrk5xY2HYRa8v4jEqJX2aXRP9UhkCu6GQtraeyrlo2GxxuTro3wBAJtEc pJsAtAWeIwHZn5u0d3HVeSfNbVvqs9Kiw7UkhoQHR9WBCxVkLwn8h84fepV2vR8OUgp1 tedQ== X-Gm-Message-State: AA+aEWbixOXuZWzrfY5RCJ4YcLiQQ8KOwKm/51TrpQc5gTWkBGWKZDs0 EazYMVGfCuOUtbFJCP680F1GZA== X-Google-Smtp-Source: AFSGD/WWGVqhlLV9N+gy7/L0h+SWI0D43IjjT0rGR6k0Kvty7i95ZbRVRtotKakhZvt76ifl6eZlTw== X-Received: by 2002:a17:902:9698:: with SMTP id n24-v6mr3333279plp.9.1542736941109; Tue, 20 Nov 2018 10:02:21 -0800 (PST) Received: from xeon-e3 (204-195-22-127.wavecable.com. [204.195.22.127]) by smtp.gmail.com with ESMTPSA id h8sm19177404pfo.162.2018.11.20.10.02.20 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 20 Nov 2018 10:02:20 -0800 (PST) Date: Tue, 20 Nov 2018 10:02:12 -0800 From: Stephen Hemminger To: Jeff Guo Cc: marko.kovacevic@intel.com, john.mcnamara@intel.com, qi.z.zhang@intel.com, ferruh.yigit@intel.com, thomas@monjalon.net, dev@dpdk.org, helin.zhang@intel.com, konstantin.ananyev@intel.com, shaopeng.he@intel.com, bruce.richardson@intel.com, gaetan.rivet@6wind.com Message-ID: <20181120100212.150a6c73@xeon-e3> In-Reply-To: <1542726571-121934-1-git-send-email-jia.guo@intel.com> References: <1542726571-121934-1-git-send-email-jia.guo@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] [PATCH] doc: add known igb_uio device hot-unplug issue X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Nov 2018 18:02:22 -0000 On Tue, 20 Nov 2018 23:09:31 +0800 Jeff Guo wrote: > 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 > --- > 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. Surely this is fixable. What is the back trace in the kernel? How can it be reproduced with some common hardware (or hypervisor). Will it happen with KVM?