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=-0.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED autolearn=no 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 B7E4FC352A2 for ; Thu, 6 Feb 2020 10:12:59 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 8CB0920658 for ; Thu, 6 Feb 2020 10:12:59 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=btinternet.com header.i=@btinternet.com header.b="TjoHl9JS" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728360AbgBFKM7 (ORCPT ); Thu, 6 Feb 2020 05:12:59 -0500 Received: from mailomta28-sa.btinternet.com ([213.120.69.34]:61720 "EHLO sa-prd-fep-048.btinternet.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727864AbgBFKM6 (ORCPT ); Thu, 6 Feb 2020 05:12:58 -0500 X-Greylist: delayed 1329 seconds by postgrey-1.27 at vger.kernel.org; Thu, 06 Feb 2020 05:12:57 EST Received: from sa-prd-rgout-005.btmx-prd.synchronoss.net ([10.2.38.8]) by sa-prd-fep-048.btinternet.com with ESMTP id <20200206101255.QDR16397.sa-prd-fep-048.btinternet.com@sa-prd-rgout-005.btmx-prd.synchronoss.net>; Thu, 6 Feb 2020 10:12:55 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btinternet.com; s=btmx201904; t=1580983975; bh=LfeypBNiqzzaMzbEcIUFIRZRTd+WhpIbUIZyDxiZC1E=; h=Message-ID:Subject:From:To:Cc:Date:MIME-Version; b=TjoHl9JSibaMqfkP0DDQ1UXRT8a49Ku7nd3Jc77T+lh9pMUsyEZEylPhdVH/ztckaMt861FquU3Su9VYFPRZ4hGeon6exEGtKOErBeLixIgTsjBaEk9tp8VAT0zwNwIIORfvmr6gqa19SoFOwLaGcZzyCtBWrByUCjSETeqKaDKvn3/y+sv9mqLoaosjMjAUDqtJVFcfiCHzjkVflk+FnI53zRbb/FpTKo5t3eLxvm/BUvd45dxZ1ohktFUKFOdZMEoHlIih/Ajmp7TVvSeflaRWVfm3WsIiBOvqywa/2grLPlKqyI9aVmfh/y2i+3q+s8nZaIb9NYaRU6M1T6hR+Q== Authentication-Results: btinternet.com; auth=pass (PLAIN) smtp.auth=richard_c_haines@btinternet.com X-Originating-IP: [86.134.5.31] X-OWM-Source-IP: 86.134.5.31 (GB) X-OWM-Env-Sender: richard_c_haines@btinternet.com X-VadeSecure-score: verdict=clean score=0/300, class=clean X-RazorGate-Vade: gggruggvucftvghtrhhoucdtuddrgedugedrheefgdduvdcutefuodetggdotefrodftvfcurfhrohhfihhlvgemuceutffkvffkuffjvffgnffgvefqofdpqfgfvfenuceurghilhhouhhtmecufedttdenucenucfjughrpefkuffhvffftggfggfgsehtjeertddtreejnecuhfhrohhmpeftihgthhgrrhguucfjrghinhgvshcuoehrihgthhgrrhgupggtpghhrghinhgvshessghtihhnthgvrhhnvghtrdgtohhmqeenucffohhmrghinhepkhgvrhhnvghlrdhorhhgnecukfhppeekiedrudefgedrhedrfedunecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehhvghloheplhhotggrlhhhohhsthdrlhhotggrlhguohhmrghinhdpihhnvghtpeekiedrudefgedrhedrfedupdhmrghilhhfrhhomhepoehrihgthhgrrhgupggtpghhrghinhgvshessghtihhnthgvrhhnvghtrdgtohhmqecuuefqffgjpeekuefkvffokffogfdprhgtphhtthhopeeoughhohifvghllhhssehrvgguhhgrthdrtghomheqpdhrtghpthhtohepoehlihhnuhigqdhfshguvghvvghlsehvghgvrhdrkhgvrhhnvghlrdhorhhgqedprhgtphhtthhopeeoohhmohhsnhgrtggvsehrvgguhhgrthdrtghomheqpdhrtghpthhtohepoehprghulhesphgruhhlqdhmohhorhgvrdgtohhmqedprhgtphhtthhopeeorhhitghhrghruggptggphhgrihhnvghssehhohhtmhgrihhlrdgtohhmqedprhgtphhtthhopeeoshgu shesthihtghhohdrnhhsrgdrghhovheqpdhrtghpthhtohepoehsvghlihhnuhigsehvghgvrhdrkhgvrhhnvghlrdhorhhgqedprhgtphhtthhopeeovhhirhhoseiivghnihhvrdhlihhnuhigrdhorhhgrdhukheq X-RazorGate-Vade-Verdict: clean 0 X-RazorGate-Vade-Classification: clean Received: from localhost.localdomain (86.134.5.31) by sa-prd-rgout-005.btmx-prd.synchronoss.net (5.8.340) (authenticated as richard_c_haines@btinternet.com) id 5E3A290C003AEDC8; Thu, 6 Feb 2020 10:12:55 +0000 Message-ID: Subject: Test to trace kernel bug in fsconfig(2) with nfs From: Richard Haines To: linux-fsdevel@vger.kernel.org Cc: selinux@vger.kernel.org, dhowells@redhat.com, viro@zeniv.linux.org.uk, sds@tycho.nsa.gov, paul@paul-moore.com, omosnace@redhat.com Date: Thu, 06 Feb 2020 10:12:54 +0000 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: linux-fsdevel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-fsdevel@vger.kernel.org The test program 'fsmount.c' sent in [1], can be used along with the test script below to show a kernel bug when calling fsconfig(2) with any valid option for an nfs mounted filesystem. This problem is not related to the btrfs bug I reported in [1], however I suspect that once vanilla NFS options can be set, it may uncover the same issue as in [1]. [1] https://lore.kernel.org/selinux/c02674c970fa292610402aa866c4068772d9ad4e.camel@btinternet.com/T/#u Copy the statements below into nfs-test.sh and run. MOUNT=/home # must be a top-level mount TESTDIR=$MOUNT/MOUNT-FS-MULTI/selinux-testsuite systemctl start nfs-server exportfs -orw,no_root_squash,security_label localhost:$MOUNT mkdir -p /mnt/selinux-testsuite # mount works: #mount -t nfs -o "vers=4.2,rootcontext=system_u:object_r:unconfined_t:s0" localhost:$TESTDIR /mnt/selinux-testsuite # Both of these give: Failed fsconfig(2): Invalid argument (nfsvers=4.2 or vers=4.2 fail) ./fsmount nfs localhost.localdomain:$TESTDIR /mnt/selinux-testsuite "nfsvers=4.2" #./fsmount nfs localhost.localdomain:$TESTDIR /mnt/selinux-testsuite "nfsvers=4.2,rootcontext=system_u:object_r:unconfined_t:s0" umount /mnt/selinux-testsuite exportfs -u localhost:$MOUNT systemctl stop nfs-server