Date: Sun, 4 Sep 2016 20:33:52 +0300 From: Andriy Gapon <avg@FreeBSD.org> To: Konstantin Belousov <kostikbel@gmail.com> Cc: Frederic Chardon <chardon.frederic@gmail.com>, freebsd-stable@FreeBSD.org, freebsd-current@FreeBSD.org Subject: Re: Regression with revision 303970 (was kern.proc.pathname failure while booting from zfs) Message-ID: <ef71059f-33d2-0713-37f2-13bcc0cde5d6@FreeBSD.org> In-Reply-To: <20160904145103.GD83214@kib.kiev.ua> References: <CAMODbknGPaXR3=v-caacyigP5MdDgc9DKhAq=FMWh5=r7GzoDA@mail.gmail.com> <1aebfb2b-5df6-abe0-686f-b170fdaef510@FreeBSD.org> <b7e6ace7-ec52-4bdb-0185-ef6bcddb371e@FreeBSD.org> <20160904145103.GD83214@kib.kiev.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On 04/09/2016 17:51, Konstantin Belousov wrote: > It is only masked when name cache has an entry for the vnode. So sometimes > vn_fullpath() should be broken even if no normalization is applied. Yes, this is true. > OTOH, classic filesystems like UFS do not have any other means to translate > non-directory inode to name and parent at all, except the namecache hint. In fact, this is true for ZFS as well. While ZFS znodes have an attribute that specifies a (single) parent, it's obviously unreliable for files, because a file can be linked into multiple directories and then unlinked from a directory specified by the attribute. So, at the moment I do not have any good ideas on how to make this work. Maybe trying to use the parent attribute and failing when it's inconsistent would be good enough... -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ef71059f-33d2-0713-37f2-13bcc0cde5d6>