Date: Tue, 08 Nov 2016 14:33:21 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 214326] nullfs Message-ID: <bug-214326-8@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
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.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-214326-8>