From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-6.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI, SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 3153EC33CA2 for ; Sun, 12 Jan 2020 16:04:05 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id C44A0214D8 for ; Sun, 12 Jan 2020 16:04:04 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=btinternet.com header.i=@btinternet.com header.b="BTcnmboE" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1733081AbgALQEE (ORCPT ); Sun, 12 Jan 2020 11:04:04 -0500 Received: from mailomta31-re.btinternet.com ([213.120.69.124]:20769 "EHLO re-prd-fep-042.btinternet.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1733064AbgALQEE (ORCPT ); Sun, 12 Jan 2020 11:04:04 -0500 Received: from re-prd-rgout-002.btmx-prd.synchronoss.net ([10.2.54.5]) by re-prd-fep-042.btinternet.com with ESMTP id <20200112160401.XCWG28894.re-prd-fep-042.btinternet.com@re-prd-rgout-002.btmx-prd.synchronoss.net>; Sun, 12 Jan 2020 16:04:01 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btinternet.com; s=btmx201904; t=1578845041; bh=pQfztX9AgnaGWWJk9oMxL0Id/lE+upuZYV4dHj/TORU=; h=Message-ID:Subject:From:To:Cc:Date:In-Reply-To:References:MIME-Version; b=BTcnmboEWfNv+kIZOWwTHpcEqJeHITL4N2MCQhztLfsROvRXRPIPq8zPiuAqrfF1+s8GcE4pDG8jKUl4xHu+oQOwmjG2l1V38H1OtqVO4iUkiu1ZkIbuEDIbt57YgJXYWxqgZsvSqKqV0iq8pwRoZ93lQ4j7ljgX5zZn8Yes8hfTokNfyDLhz4E6QGcX5Ba4EIjGRujdaYV0qUbvcZlrIOUAnvZU7jwNt5obUY0Rr6gLI5Di+NJzgX0vizMAPFBbiwvnK2G+ZJxaah5pL2MvgwBQ8WgV35WyMrdya1JSkxJ3fNKH1m0/HQWWCJ4azuwizRKSnCedqliilds63JtJnQ== Authentication-Results: btinternet.com; auth=pass (PLAIN) smtp.auth=richard_c_haines@btinternet.com X-Originating-IP: [86.134.6.171] X-OWM-Source-IP: 86.134.6.171 (GB) X-OWM-Env-Sender: richard_c_haines@btinternet.com X-VadeSecure-score: verdict=clean score=0/300, class=clean X-RazorGate-Vade: gggruggvucftvghtrhhoucdtuddrgedufedrvdeikedgkeefucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuueftkffvkffujffvgffngfevqffopdfqfgfvnecuuegrihhlohhuthemuceftddtnecunecujfgurhepkffuhffvffgjfhgtfggggfesthejredttderjeenucfhrhhomheptfhitghhrghrugcujfgrihhnvghsuceorhhitghhrghruggptggphhgrihhnvghssegsthhinhhtvghrnhgvthdrtghomheqnecukfhppeekiedrudefgedriedrudejudenucfrrghrrghmpehhvghloheplhhotggrlhhhohhsthdrlhhotggrlhguohhmrghinhdpihhnvghtpeekiedrudefgedriedrudejuddpmhgrihhlfhhrohhmpeeorhhitghhrghruggptggphhgrihhnvghssegsthhinhhtvghrnhgvthdrtghomhequceuqfffjgepkeeukffvoffkoffgpdhrtghpthhtohepoehomhhoshhnrggtvgesrhgvughhrghtrdgtohhmqedprhgtphhtthhopeeorhhitghhrghruggptggphhgrihhnvghssehhohhtmhgrihhlrdgtohhmqedprhgtphhtthhopeeoshgushesthihtghhohdrnhhsrgdrghhovheqpdhrtghpthhtohepoehsvghlihhnuhigsehvghgvrhdrkhgvrhhnvghlrdhorhhgqeenucevlhhushhtvghrufhiiigvpedt X-RazorGate-Vade-Verdict: clean 0 X-RazorGate-Vade-Classification: clean Received: from localhost.localdomain (86.134.6.171) by re-prd-rgout-002.btmx-prd.synchronoss.net (5.8.337) (authenticated as richard_c_haines@btinternet.com) id 5DE2575E0785CB0E; Sun, 12 Jan 2020 16:04:01 +0000 Message-ID: Subject: Re: [PATCH V2 1/1] selinux-testsuite: Add filesystem tests From: Richard Haines To: Stephen Smalley , selinux@vger.kernel.org Cc: omosnace@redhat.com Date: Sun, 12 Jan 2020 16:04:00 +0000 In-Reply-To: References: <20200109150709.360345-1-richard_c_haines@btinternet.com> <20200109150709.360345-2-richard_c_haines@btinternet.com> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.34.2 (3.34.2-1.fc31) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: selinux-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: selinux@vger.kernel.org On Fri, 2020-01-10 at 13:18 -0500, Stephen Smalley wrote: > On 1/10/20 1:09 PM, Richard Haines wrote: > > On Thu, 2020-01-09 at 12:19 -0500, Stephen Smalley wrote: > > > On 1/9/20 10:07 AM, Richard Haines wrote: > > > > Test filesystem permissions and setfscreatecon(3). > > > > > > > > From kernels 5.5 filesystem { watch } is also tested. > > > > > > > > Signed-off-by: Richard Haines > > > > --- > > > > diff --git a/policy/test_filesystem.te > > > > b/policy/test_filesystem.te > > > > new file mode 100644 > > > > index 0000000..2eee1fc > > > > --- /dev/null > > > > +++ b/policy/test_filesystem.te > > > > @@ -0,0 +1,324 @@ > > > > +# > > > > +######### Test filesystem permissions policy module ########## > > > > +# > > > > +attribute filesystemdomain; > > > > + > > > > +#################### Create a test file context > > > > ###################### > > > > +type test_filesystem_filecon_t; > > > > +unconfined_runs_test(test_filesystem_filecon_t) > > > > + > > > > +################# Test all functions > > > > ########################## > > > > +type test_filesystem_t; > > > > +domain_type(test_filesystem_t) > > > > +unconfined_runs_test(test_filesystem_t) > > > > +typeattribute test_filesystem_t testdomain; > > > > +typeattribute test_filesystem_t filesystemdomain; > > > > + > > > > +allow test_filesystem_t self:capability { sys_admin }; > > > > +allow test_filesystem_t self:filesystem { mount remount > > > > quotamod > > > > relabelfrom relabelto unmount quotaget }; > > > > +allow test_filesystem_t self:dir { mounton add_name write }; > > > > +allow test_filesystem_t test_file_t:dir { mounton write > > > > remove_name rmdir }; > > > > +# Create test file > > > > +allow test_filesystem_t self:dir { add_name write }; > > > > +allow test_filesystem_t self:file { create relabelfrom > > > > relabelto > > > > }; > > > > + > > > > +fs_mount_all_fs(test_filesystem_t) > > > > +fs_remount_all_fs(test_filesystem_t) > > > > +fs_unmount_all_fs(test_filesystem_t) > > > > +fs_relabelfrom_all_fs(test_filesystem_t) > > > > +fs_get_xattr_fs_quotas(test_filesystem_t) > > > > +files_search_all(test_filesystem_t) > > > > +# Required for mount opts > > > > "rootcontext=system_u:object_r:test_filesystem_t:s0"; > > > > +fs_associate(test_filesystem_t) > > > > +fs_getattr_xattr_fs(test_filesystem_t) > > > > + > > > > +# For running quotacheck(8) > > > > +files_type(test_filesystem_t) > > > > +# Update quotas > > > > +fs_set_all_quotas(test_filesystem_t) > > > > +allow test_filesystem_t self:file { quotaon }; > > > > +# Create test file and change context: > > > > +fs_associate(test_filesystem_filecon_t) > > > > +allow test_filesystem_t test_filesystem_filecon_t:file { open > > > > read > > > > getattr relabelto write }; > > > > +dontaudit test_filesystem_t kernel_t:process { setsched }; > > > > > > Why do you need these dontaudit statements? It seems like a > > > kernel > > > bug > > > if something is triggering a setsched permission check on the > > > kernel_t > > > domain? Something the kernel module is doing during > > > initialization? > > > > > > > I've tracked this down to them all being called from block/ioprio.c > > with: security_task_setioprio(task, ioprio) -> > > selinux_task_setioprio > > > > Why the SECCLASS_PROCESS, PROCESS__SETSCHED I've no idea. The > > following > > also use SET/GETSCHED permission: > > > > selinux_task_getioprio, selinux_task_setnice, > > selinux_task_movememory > > The confusing bit is that it is between test_filesystem_t and > kernel_t. > If the process was setting its own ioprio, then I'd expect to see > the > denial between test_filesystem_t and test_filesystem_t aka self. If > the > process inserted a kernel module and the module initializer spawned > a > kernel thread that set its ioprio, I would expect it to be kernel_t > to > kernel_t. Some more info on who calls set_task_ioprio: fs/ext4/super.c calls 'set_task_ioprio' in two places using: set_task_ioprio(sbi->s_journal->j_task, journal_ioprio); The return codes are not checked. This code was added 11 years ago. fs/btrfs/reada.c also calls 'set_task_ioprio' in two places using: set_task_ioprio(current, BTRFS_IOPRIO_READA); The return codes are not checked. As can be seen the ext4 module does not use 'current'. I have patched kernel 5.5-rc5 to use 'current' and it now works as you expected. Also the kernel_t:process { setsched } rules can be removed. As the problem will exist for some time, I've added to the test policy: kernel_dontaudit_setsched(filesystemdomain) It appears that most of the refpolicy modules do the same.