From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Subject: Re: [PATCH 13/38] tomoyo: Implement security hooks for the new mount API [ver #10] To: David Howells Cc: viro@zeniv.linux.org.uk, tomoyo-dev-en@lists.sourceforge.jp, linux-security-module@vger.kernel.org, torvalds@linux-foundation.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org References: <153271267980.9458.7640156373438016898.stgit@warthog.procyon.org.uk> <153271277078.9458.16912166489973051987.stgit@warthog.procyon.org.uk> From: Tetsuo Handa Message-ID: Date: Sat, 28 Jul 2018 11:29:57 +0900 MIME-Version: 1.0 In-Reply-To: <153271277078.9458.16912166489973051987.stgit@warthog.procyon.org.uk> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: On 2018/07/28 2:32, David Howells wrote: > Implement the security hook to check the creation of a new mountpoint for > Tomoyo. > > As far as I can tell, Tomoyo doesn't make use of the mount data or parse > any mount options, so I haven't implemented any of the fs_context hooks for > it. > > Signed-off-by: David Howells > cc: Tetsuo Handa > cc: tomoyo-dev-en@lists.sourceforge.jp > cc: linux-security-module@vger.kernel.org Would you provide examples of each possible combination as a C program? For example, if one mount point from multiple sources with different options are possible, please describe such pattern using syscall so that LSM modules can run it to see whether they are working as expected.