From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Howells Subject: Re: [PATCH 18/27] bpf: Restrict kernel image access functions when the kernel is locked down Date: Mon, 23 Oct 2017 15:53:00 +0100 Message-ID: <21530.1508770380@warthog.procyon.org.uk> 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> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Return-path: In-Reply-To: <20171020164343.e5mlq7ukskfjmlpp@linux-rasp2> Content-ID: <21529.1508770380.1@warthog.procyon.org.uk> Sender: linux-kernel-owner@vger.kernel.org To: jlee@suse.com Cc: dhowells@redhat.com, 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 List-Id: linux-efi@vger.kernel.org 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. David