From owner-freebsd-bugs@freebsd.org Tue Nov 8 14:33:21 2016 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4E8BCC37A03 for ; Tue, 8 Nov 2016 14:33:21 +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 mx1.freebsd.org (Postfix) with ESMTPS id 3EE34B17 for ; Tue, 8 Nov 2016 14:33:21 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id uA8EXL1g079012 for ; Tue, 8 Nov 2016 14:33:21 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 214326] nullfs Date: Tue, 08 Nov 2016 14:33:21 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: root@linkage.white-void.net X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter attachments.created Message-ID: 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-bugs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Nov 2016 14:33:21 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D214326 Bug ID: 214326 Summary: nullfs Product: Base System Version: 10.3-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: root@linkage.white-void.net Created attachment 176786 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D176786&action= =3Dedit An experimental patch for unionfs internal cache(Nov 8, 2016) ** This report may be related to, or duplicate of Bug #186360 ** With unionfs+nullfs, I saw a strange behaviour. # mkdir mountfrom1 mountfrom2 mountto # mkdir mountfrom1/a # touch mountfrom2/b # mount -t unionfs mountfrom1 mountto # mount -t nullfs mountfrom2 mountto/a # ls mountto/a/b ls: mountto/a/b: No such file or directory # ls mountto/a b # ls mountto/a/b mountto/a/b I digged into unionfs module, and found 'unionfs_lookup' is returning diffe= rent vnode for same single object 'a', for mount and later "ls" command. It is caused by a bug in unionfs's internal cache (I think), and I solved it with an attached patch. Well, my patch omits a check for 'ISLASTCN', but I don't know why the check= is needed. --=20 You are receiving this mail because: You are the assignee for the bug.=