From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by dpdk.org (Postfix) with ESMTP id E32081BEFD for ; Wed, 27 Jun 2018 16:39:05 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 6ECB321D42; Wed, 27 Jun 2018 10:39:05 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Wed, 27 Jun 2018 10:39:05 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=VR7M0WbwIed/IIi6Xv7gm0Sm/I jzxBuSrJbpeqnoT/8=; b=erRqKIyuIVHCc8aZOYTJk5c8w7F4/ePpOJSbfcBEVb szgFWTDltRbJVAB24OhyBg3nu3wucBywvDbmUeaWasLTmf4E6rf5NqCv1KRg11+6 tJGhGPnE726a9jcXDH7WH1DfvWXoO+WNeWgQtuN7FFLSxSiBMJG1vYF49go9dsKb s= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=VR7M0W bwIed/IIi6Xv7gm0Sm/IjzxBuSrJbpeqnoT/8=; b=aRGWVpn2gyPtxIlDjW+M0I HdIX5txZ4vLIBgt3ddEGpB5v1ao4Stchaax4ITeRP6fVRNWt2fjzfos9V779u6pa aoxdM6tMueT49ekm93UsyA4VtNAHd95KmZIdDHPrBOXehOcwR2nP+C+RzvAFrC+1 fTODMfT8MJc5x9Tk+4+RuOeu/C1W/3qNKeQc4NvMM74vZjOdnZIOpEor2hwcTeXi EzaUTxycWhZmkdwEYPxwwyVK+FaPfUQuqwNderWU3aIT4mAY7uvWUuJoDRufifkE sLh26GpO7QZgupW+VwgOwCdFvEra2+Z+x7df1ZoPkqjsiOWd3AA0Q7PTjzBiCXpA == X-ME-Proxy: X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 9DFCD103DC; Wed, 27 Jun 2018 10:39:02 -0400 (EDT) From: Thomas Monjalon To: Ferruh Yigit Cc: dev@dpdk.org, Christian Ehrhardt , Luca Boccassi , Maxime Coquelin , Neil Horman , Stephen Hemminger Date: Wed, 27 Jun 2018 16:39:01 +0200 Message-ID: <17193107.8HUzy7Nv4o@xps> In-Reply-To: <20180516144220.21235-1-ferruh.yigit@intel.com> References: <20180516101851.2443-1-ferruh.yigit@intel.com> <20180516144220.21235-1-ferruh.yigit@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v3] igb_uio: fail and log if kernel lock down is enabled 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: Wed, 27 Jun 2018 14:39:06 -0000 16/05/2018 16:42, Ferruh Yigit: > When EFI secure boot is enabled, it is possible to lock down kernel and > prevent accessing device BARs and this makes igb_uio unusable. > > Lock down patches are not part of the vanilla kernel but they are > applied and used by some distros already [1]. > > It is not possible to fix this issue, but intention of this patch is to > detect and log if kernel lock down enabled and don't insert the module > for that case. > > The challenge is since this feature enabled by distros, they have > different config options and APIs for it. This patch is done based on > Fedora and Ubuntu kernel source, may needs to add more distro specific > support. > > [1] > kernel.ubuntu.com/git/ubuntu/ubuntu-artful.git/commit/?id=99f9ef18d5b6 > And a few more patches to > > Signed-off-by: Ferruh Yigit > Acked-by: Luca Boccassi Applied, thanks