From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753155AbdJTQos (ORCPT ); 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 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 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 mboxrd@z Thu Jan 1 00:00:00 1970 From: jlee@suse.com (jlee at suse.com) Date: Sat, 21 Oct 2017 00:43:43 +0800 Subject: [PATCH 18/27] bpf: Restrict kernel image access functions when the kernel is locked down In-Reply-To: <19424.1508515402@warthog.procyon.org.uk> 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> Message-ID: <20171020164343.e5mlq7ukskfjmlpp@linux-rasp2> To: linux-security-module@vger.kernel.org List-Id: linux-security-module.vger.kernel.org On Fri, Oct 20, 2017 at 05:03:22PM +0100, David Howells wrote: > jlee at 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 -- To unsubscribe from this list: send the line "unsubscribe linux-security-module" in the body of a message to majordomo at vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html