From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752364AbdCAJ4N (ORCPT ); Wed, 1 Mar 2017 04:56:13 -0500 Received: from namei.org ([65.99.196.166]:34066 "EHLO namei.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752078AbdCAJep (ORCPT ); Wed, 1 Mar 2017 04:34:45 -0500 Date: Wed, 1 Mar 2017 20:32:27 +1100 (AEDT) From: James Morris To: =?ISO-8859-15?Q?Micka=EBl_Sala=FCn?= cc: linux-kernel@vger.kernel.org, Alexei Starovoitov , Andy Lutomirski , Arnaldo Carvalho de Melo , Casey Schaufler , Daniel Borkmann , David Drysdale , "David S . Miller" , "Eric W . Biederman" , James Morris , Jann Horn , Jonathan Corbet , Matthew Garrett , Michael Kerrisk , Kees Cook , Paul Moore , Sargun Dhillon , "Serge E . Hallyn" , Shuah Khan , Tejun Heo , Thomas Graf , Will Drewry , kernel-hardening@lists.openwall.com, linux-api@vger.kernel.org, linux-security-module@vger.kernel.org, netdev@vger.kernel.org Subject: Re: [PATCH v5 03/10] bpf: Define handle_fs and add a new helper bpf_handle_fs_get_mode() In-Reply-To: <20170222012632.4196-4-mic@digikod.net> Message-ID: References: <20170222012632.4196-1-mic@digikod.net> <20170222012632.4196-4-mic@digikod.net> User-Agent: Alpine 2.20 (LRH 67 2015-01-07) MIME-Version: 1.0 Content-Type: multipart/mixed; BOUNDARY="1665246916-612674400-1488360751=:9253" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --1665246916-612674400-1488360751=:9253 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT On Wed, 22 Feb 2017, Mickaël Salaün wrote: > Add an eBPF function bpf_handle_fs_get_mode(handle_fs) to get the mode > of a an abstract object wrapping either a file, a dentry, a path, or an > inode. > > Changes since v4: > * use a file abstraction (handle) to wrap inode, dentry, path and file > structs Good to see these abstractions. As discussed at LPC, we need to ensure that we don't couple the Landlock API too closely with the LSM API, as the former is an ABI exposed to userland -- we don't want to lose the ability to change LSM internally due to breaking Landlock policies. > @@ -82,6 +87,8 @@ enum bpf_arg_type { > > ARG_PTR_TO_CTX, /* pointer to context */ > ARG_ANYTHING, /* any (initialized) argument is ok */ > + > + ARG_CONST_PTR_TO_HANDLE_FS, /* pointer to an abstract FS struct */ > }; Extraneous whitespace? -- James Morris --1665246916-612674400-1488360751=:9253--