From mboxrd@z Thu Jan 1 00:00:00 1970 From: James Morris Subject: Re: [PATCH v17 05/10] fs,landlock: Support filesystem access-control Date: Fri, 15 May 2020 05:37:03 +1000 (AEST) Message-ID: References: <20200511192156.1618284-1-mic@digikod.net> <20200511192156.1618284-6-mic@digikod.net> <2561827e-020c-9a76-98ae-9514904c69f9@digikod.net> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="1665246916-72433049-1589485024=:7929" Return-path: List-Post: List-Help: List-Unsubscribe: List-Subscribe: In-Reply-To: <2561827e-020c-9a76-98ae-9514904c69f9@digikod.net> To: =?ISO-8859-15?Q?Micka=EBl_Sala=FCn?= Cc: Casey Schaufler , linux-kernel@vger.kernel.org, Al Viro , Andy Lutomirski , Arnd Bergmann , Jann Horn , Jonathan Corbet , Kees Cook , Michael Kerrisk , =?ISO-8859-15?Q?Micka=EBl_Sala=FCn?= , "Serge E . Hallyn" , Shuah Khan , Vincent Dagonneau , kernel-hardening@lists.openwall.com, linux-api@vger.kernel.org, linux-arch@vger.kernel.org, linux-doc@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-kselftest@vger.kernel.org, linux-security-module@vger.kernel.org, x86@kernel.org List-Id: linux-arch.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-72433049-1589485024=:7929 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8BIT On Thu, 14 May 2020, Mickaël Salaün wrote: > > fsnotify is not an LSM. > > Yes, so I'll need to add a new LSM hook for this (release) call, right? Unless an existing one will work. -- James Morris --1665246916-72433049-1589485024=:7929-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from namei.org ([65.99.196.166]:59072 "EHLO namei.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726667AbgENThj (ORCPT ); Thu, 14 May 2020 15:37:39 -0400 Date: Fri, 15 May 2020 05:37:03 +1000 (AEST) From: James Morris Subject: Re: [PATCH v17 05/10] fs,landlock: Support filesystem access-control In-Reply-To: <2561827e-020c-9a76-98ae-9514904c69f9@digikod.net> Message-ID: References: <20200511192156.1618284-1-mic@digikod.net> <20200511192156.1618284-6-mic@digikod.net> <2561827e-020c-9a76-98ae-9514904c69f9@digikod.net> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="1665246916-72433049-1589485024=:7929" Sender: linux-arch-owner@vger.kernel.org List-ID: To: =?ISO-8859-15?Q?Micka=EBl_Sala=FCn?= Cc: Casey Schaufler , linux-kernel@vger.kernel.org, Al Viro , Andy Lutomirski , Arnd Bergmann , Jann Horn , Jonathan Corbet , Kees Cook , Michael Kerrisk , =?ISO-8859-15?Q?Micka=EBl_Sala=FCn?= , "Serge E . Hallyn" , Shuah Khan , Vincent Dagonneau , kernel-hardening@lists.openwall.com, linux-api@vger.kernel.org, linux-arch@vger.kernel.org, linux-doc@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-kselftest@vger.kernel.org, linux-security-module@vger.kernel.org, x86@kernel.org Message-ID: <20200514193703.J1EnfJapqzG12nTadckJWVX_9j-nxpexhkfp0WsEQuE@z> 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-72433049-1589485024=:7929 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8BIT On Thu, 14 May 2020, Mickaël Salaün wrote: > > fsnotify is not an LSM. > > Yes, so I'll need to add a new LSM hook for this (release) call, right? Unless an existing one will work. -- James Morris --1665246916-72433049-1589485024=:7929--