Received: by 10.223.164.221 with SMTP id h29csp1449978wrb; Wed, 25 Oct 2017 00:08:40 -0700 (PDT) X-Google-Smtp-Source: ABhQp+QHAW0Lvv3kU1TUD9aZV7zyHYbU92eR4NkoF/sf8L7imWm/OYD7OMvPU8n6X+d5AK8uRBst X-Received: by 10.99.7.208 with SMTP id 199mr1147504pgh.158.1508915320344; Wed, 25 Oct 2017 00:08:40 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1508915320; cv=none; d=google.com; s=arc-20160816; b=U3cvQarmAatPKlIasjrjaXqBQQAMlvGfwNGliF18a3srRJkBom/OblUtgMzwPnNBQt ZSsPZ5RaI31axvQEbhPNI1pKArbikvHPQRk2kGtTC6PHQIFj97pFbWiiGAeMjYvd6daK Tzza6MH51RfQBZ0wQbEcrx/8r+YZrTXJX1UTuLwo8ZkHrIS55a7+zVuvt7xbijtIcL8y LUzyrDkuaBlG+BbByzaU6d5vYhGiIa2sA2MuIK3S0GXR3h12e9iaveRcYjm6pkv8sgtY ehCsio/BVo8l3zR94k0Xiioc5cq7dAYyGWkyU+N5Vj1uJFO+BlPltiUtLnMHL/XlxoIy qWAA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=NBZH2VcBXmxuTAOqtIVBbFujmI2ZbrUVQm3VRgTRBM8=; b=N4pEXozjf84OO3fyzZO2gaz1/YAKasOOA+nBC3ggVin1GNTm9fps3CFDH1aqViVRSL MhGqP06YUhxO1ulRUbRpRb22U7eW8pqaJtJE9LJX9upkzNVdwFNkiHJgMyKpstS/3Lwn 6AoP2R+ZVela+JKIeNbOHBJZldVC3bq9CwpyQ+lviaFtlwrT1YSQJDyMFJVC4xfqMBBZ CzGX2inyGxBWWbO5mH7pBStwXf29bgqWfl/fRTAdQODliWJ0vS0nX1x28yiOP1fGzB8H bSfzbhvUkxwxUzfdVZlpkxUFnzASP5gCAK0WVi0UmzCXJIr2zW0665uRpboxFnUQvHR4 ID7Q== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id a3si1514395pfc.196.2017.10.25.00.08.26; Wed, 25 Oct 2017 00:08:40 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752099AbdJYHHr (ORCPT + 99 others); Wed, 25 Oct 2017 03:07:47 -0400 Received: from smtp.nue.novell.com ([195.135.221.5]:34281 "EHLO smtp.nue.novell.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751425AbdJYHHo (ORCPT ); Wed, 25 Oct 2017 03:07:44 -0400 Received: from linux-l9pv.suse (unknown.telstraglobal.net [134.159.103.118]) by smtp.nue.novell.com with ESMTP (TLS encrypted); Wed, 25 Oct 2017 09:07:37 +0200 Date: Wed, 25 Oct 2017 15:07:30 +0800 From: joeyli To: David Howells Cc: Alexei Starovoitov , linux-security-module@vger.kernel.org, gnomes@lxorguk.ukuu.org.uk, linux-efi@vger.kernel.org, matthew.garrett@nebula.com, gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org, jforbes@redhat.com, Daniel Borkmann , "David S. Miller" , netdev@vger.kernel.org, Gary Lin Subject: Re: [PATCH 18/27] bpf: Restrict kernel image access functions when the kernel is locked down Message-ID: <20171025070730.GH8550@linux-l9pv.suse> References: <20171020164343.e5mlq7ukskfjmlpp@linux-rasp2> <20171020155748.kzrvg6565oxh6gmb@linux-rasp2> <20171020024732.GJ3285@linux-l9pv.suse> <150842463163.7923.11081723749106843698.stgit@warthog.procyon.org.uk> <150842476953.7923.18174368926573855810.stgit@warthog.procyon.org.uk> <20171019221829.7m5nczg3ltqmhzom@ast-mbp> <2582.1508486928@warthog.procyon.org.uk> <19424.1508515402@warthog.procyon.org.uk> <21530.1508770380@warthog.procyon.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <21530.1508770380@warthog.procyon.org.uk> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Oct 23, 2017 at 03:53:00PM +0100, David Howells wrote: > jlee@suse.com wrote: > > > hm... patch 4 only prevents write_mem() but not read_mem(). > > Or I missed anything? > > Actually, yes, as it happens, patch 11 prevents you from even opening /dev/mem > and /dev/kmem by locking down open of /dev/port. So I've moved this bit to > patch 4, simplified and posted a new variant for patch 4. > Thank you for pointing out! Joey Lee From 1582060450552078825@xxx Mon Oct 23 14:53:38 +0000 2017 X-GM-THRID: 1581706293786105139 X-Gmail-Labels: Inbox,Category Forums