From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: Re: [PATCH] igb_uio: fail and log if kernel lock down is enabled Date: Tue, 15 May 2018 11:52:32 -0700 Message-ID: <20180515115232.5648f749@xeon-e3> References: <20180515165612.61243-1-ferruh.yigit@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: dev@dpdk.org, Christian Ehrhardt , Luca Boccassi , Maxime Coquelin , Neil Horman To: Ferruh Yigit Return-path: Received: from mail-pg0-f65.google.com (mail-pg0-f65.google.com [74.125.83.65]) by dpdk.org (Postfix) with ESMTP id 2A8AC1B717 for ; Tue, 15 May 2018 20:52:36 +0200 (CEST) Received: by mail-pg0-f65.google.com with SMTP id w3-v6so417053pgv.12 for ; Tue, 15 May 2018 11:52:36 -0700 (PDT) In-Reply-To: <20180515165612.61243-1-ferruh.yigit@intel.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Tue, 15 May 2018 17:56:12 +0100 Ferruh Yigit wrote: > When EFI secure boot is enabled, it is possible to lock down kernel and > prevent accessing device BARs and this makes igb_uio unusable. This distro specific (and not upstream) stuff in igb_uio is getting to be a significantly ugly. Can this be detected by seeing if one of the calls (such setup bars) failing? The best long term solution would be getting all kernel modules upstream; but it looks like that will never happen due to UIO maintainer resistance.