Received: by 10.223.164.221 with SMTP id h29csp5294282wrb; Fri, 20 Oct 2017 09:45:37 -0700 (PDT) X-Google-Smtp-Source: ABhQp+REJXqzZnDzgSskTAAzVJcbu3pVZMr4/xopeHCtSOVOmgmhL12kS1/XMMmPCvgxzSZxTURc X-Received: by 10.99.168.13 with SMTP id o13mr5015600pgf.435.1508517937519; Fri, 20 Oct 2017 09:45:37 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1508517937; cv=none; d=google.com; s=arc-20160816; b=yAvfYRULaqegjk2twI83iB/lhSxxTKN1tXdUQs+d9qIO/su4FfbMN8P9pDw6c9sxsU xGe/CjWB21eghOSZXsustdXcK4dzxCEXO+h7KPNrIWmtUkYWVxF83Z7uPonWdQDGetGu Gtr7UJluaOOCqC9qMqq92PsIz/qE0RvSPnAYGw+tcL/wXbUYr07HM3LFdmstXbLOos8z LW+/2wnpOHCf/GOxUwkaI5N9imkrhZhM2sJusC4e3rCb4xc8A623c3qS6iIkg4cHpuJT AsrUVuk9vU2yZWMtzJ+GiPcciR94p8ayABXlr4g8aVQPxI+xIoPHZ9I8HlBk1voVXuji mp2g== 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=+T7BJZti3BIFuiJyRRMV2uDE2Ounhy0FEWhFgpE1Mko=; b=ngxQAlP16fZOJaSCHOoARluxg8ih3mGuE9rQ5cpexVDMYHix6FnEWCFpWJqWRzBKiI 1Jz26eDwxoXZzDIt3wWZm65ITwqybmJuCuqBtY4ElblgbWdSQxWo5/w7aQbeKr2sIHUZ pDIiQFMpck8w9T/OsT0WGVbx0C0D3uk8OQAWyrpTZNrOI/irQj4+lX1jJN6QIe1aqtRx AgNNM583WX7n+VOCgf9zxYncMdWjN7m4GAHNDzdXxpY/rmCNgvhBV90zut7d+sE/DqwH sZKXELmELuG/DERVyyk152cLPh5UBdGSUzk30j0MpzfCpOE3NyfiJ5H+KXqjiVY4uoy9 lJFQ== 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 t17si741028plo.623.2017.10.20.09.45.22; Fri, 20 Oct 2017 09:45:37 -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 S1753150AbdJTQos (ORCPT + 99 others); Fri, 20 Oct 2017 12:44:48 -0400 Received: from smtp.nue.novell.com ([195.135.221.5]:58829 "EHLO smtp.nue.novell.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752142AbdJTQoq (ORCPT ); Fri, 20 Oct 2017 12:44:46 -0400 Received: from emea4-mta.ukb.novell.com ([10.120.13.87]) by smtp.nue.novell.com with ESMTP (TLS encrypted); Fri, 20 Oct 2017 18:44:44 +0200 Received: from linux-rasp2 (nwb-a10-snat.microfocus.com [10.120.13.201]) by emea4-mta.ukb.novell.com with ESMTP (TLS encrypted); Fri, 20 Oct 2017 17:44:15 +0100 Date: Sat, 21 Oct 2017 00:43:43 +0800 From: jlee@suse.com 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: <20171020164343.e5mlq7ukskfjmlpp@linux-rasp2> References: <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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <19424.1508515402@warthog.procyon.org.uk> User-Agent: Mutt/1.6.2 (2016-07-01) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Oct 20, 2017 at 05:03:22PM +0100, David Howells wrote: > jlee@suse.com wrote: > > > I think that we don't need to lock down sys_bpf() now because > > we didn't lock down other interfaces for reading arbitrary > > address like /dev/mem and /dev/kmem. > > Ummm... See patch 4. You even gave me a Reviewed-by for it ;-) > > David hm... patch 4 only prevents write_mem() but not read_mem(). Or I missed anything? Thanks Joey Lee From 1581795195541961912@xxx Fri Oct 20 16:37:31 +0000 2017 X-GM-THRID: 1581706293786105139 X-Gmail-Labels: Inbox,Category Forums