From mboxrd@z Thu Jan 1 00:00:00 1970 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) 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=BEhRu3cH2mtQZdrftJXgnckgLzRiLxHN9RcmGOwiHLE=; b=LlSm0zXQisbNOrCFMy9ETc6AKbEp03MT8Z4iGVbr4rEkl46BjMOHfl3dY0D31fwDqG t0tGVtpkOlrS7khaCmjnaA3GpcqAxdlsnIWaT1lA8E7AZDgeUK0GNh4kPyBtRhy5RBn2 FJRveDCk/eekdnoxwDfdFHIoOO13LB5JuLvVMRGfYSg/3tS5z13p85d0qm1tJD3pbjgM qm+xMDzM7yOwaGB7viPcIU6jCUMfSd/rBfhm5k4jhT3nR/AG8DF/NlQ83GACuFNTRUx4 +fA3oJQJIzv6GolUNX+nQbiieVzbisA3BrZOtPQuTPERKGksQwQsyLEcrrmOHJENixmg jS4w== 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=BEhRu3cH2mtQZdrftJXgnckgLzRiLxHN9RcmGOwiHLE=; b=hHYc9vVmLPxmocTB8gnLQS9UNTSgEw4zEguyhgMa70MtmLBNbk7+7Ek+E3twOLTDhM gHe4fJ4lpVDoHZJjfQLMpy+Lzz7T8ClbCfz89VGkqRsGIfyAZfOo6HJE+N8iLppxpCCJ Bk6rdUCtFBXXTgWB6RYaV4rVH8WJY6Vka8sM65jKas2axaWd7HE8p/jsu1ldxdo1n8sP yIzbGw3hpWhEidDM6v6l7DEm6Z27Ph4V8kFazeRuPWgpn1DgjOo52DiqdhcfT1bKe6mG ebSc7LcthnLkmI97xdMoJGvuAvFPIH8fLFwZRnpth75TWzvnrCLX3uOLz65zeDefgWEf nG4A== X-Gm-Message-State: ALKqPwfx7BU7U9jY6Z+UqGsYmaSgTmqNJW3pGMFYHVMYzdO0Hff8XsM3 ShiqZ6ygEADxK2S1F3GTHOwFNg== X-Google-Smtp-Source: AB8JxZrGlZKTRpqdcdadOjizK2uAEzpjrFgZQauGc2Evr3oq5J1lUgywabOM/Vd3GvBee0F8jV4PQg== X-Received: by 2002:a63:9846:: with SMTP id l6-v6mr13026543pgo.217.1526410355353; Tue, 15 May 2018 11:52:35 -0700 (PDT) Received: from xeon-e3 (204-195-35-107.wavecable.com. [204.195.35.107]) by smtp.gmail.com with ESMTPSA id m9-v6sm997108pff.41.2018.05.15.11.52.34 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 15 May 2018 11:52:34 -0700 (PDT) Date: Tue, 15 May 2018 11:52:32 -0700 From: Stephen Hemminger To: Ferruh Yigit Cc: dev@dpdk.org, Christian Ehrhardt , Luca Boccassi , Maxime Coquelin , Neil Horman Message-ID: <20180515115232.5648f749@xeon-e3> In-Reply-To: <20180515165612.61243-1-ferruh.yigit@intel.com> References: <20180515165612.61243-1-ferruh.yigit@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] [PATCH] 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: Tue, 15 May 2018 18:52:36 -0000 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.