From owner-freebsd-fs@freebsd.org Fri Aug 31 12:29:32 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3F7BDF7F546 for ; Fri, 31 Aug 2018 12:29:32 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id CC0DF709F1 for ; Fri, 31 Aug 2018 12:29:31 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 8CFA1F7F545; Fri, 31 Aug 2018 12:29:31 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 69C74F7F544 for ; Fri, 31 Aug 2018 12:29:31 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 05A1A709EC for ; Fri, 31 Aug 2018 12:29:31 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 405D7214DE for ; Fri, 31 Aug 2018 12:29:30 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w7VCTUdl048416 for ; Fri, 31 Aug 2018 12:29:30 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w7VCTUDL048415 for fs@FreeBSD.org; Fri, 31 Aug 2018 12:29:30 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 212323] tests/sys/acl/01:main fails due to changes in NFSv4 ACL behavior on ^/head Date: Fri, 31 Aug 2018 12:29:29 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-STABLE X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: bugzilla.freebsd@omnilan.de X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Aug 2018 12:29:32 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212323 --- Comment #7 from Harald Schmalzbauer --- My ZFS setups suffer from an upstream ACL inheritance bug: https://www.illumos.org/issues/9722 wich is referring https://www.illumos.org/issues/8984 The latter is marked closed/solved but it is only partially solved, like the newer issue describes. I had to give up using samba for environments where NTFS ACLs are crucial. I also gave up deploying new NFSv4 ACL setups. All previous setups were damaged by the mentioned ZFS inheritance bugs. I remember many questions to be clarified regarding d and D flags (and in respect to NTFS conventions also R and W and C), but lost almost all experi= ence results. I can't tell anything about the test failure status! I just can tell that I'm observing issues regading ACL/permission mappings. Time for me to look into tests... I'm really interested in polishing our ACL implementation, but I'm lacking a good portion of standards knowledge (posix) and my lousy C skills require someone else to fix the ZFS inheritance bug first. Symlinks are one major issue to discuss regarding inheritance on ZFS =E2=80= =93 that was/is another big problem in my setups. I still have my private ACL setups (partially damaged), which is a collecti= on of special usage scenarios (e.g. users can add files and directories, but c= an't delete anything, even not their own; or shared home directory, which suffers from chmod(2) fallout due to the ACL). So it's my pleasure to test any changes and put some light in uncommon but usefuls corner cases ;-) And I'm willing to do my best to catch up with posix knowledge, but unfortunately I can't afford spending much time :-( My personal estimation was that some very skilled persons would need at lea= st a week to decide/implement and test a new/improved ACL mapping mode. My needs aren't covered by the current ACL/permission mappings =E2=80=93 no= t for NFSv4 only environments and additional CIFS/NTFS bridges were mutual destructive. Thanks, -harry --=20 You are receiving this mail because: You are the assignee for the bug.=