Date: Tue, 25 Jul 2023 17:36:25 +0000 From: bugzilla-noreply@freebsd.org To: jail@FreeBSD.org Subject: [Bug 272706] procstat(1): procstat vm in jails shows host paths of binaries and shared libraries from outside prison Message-ID: <bug-272706-29815-0MZAXJG50E@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-272706-29815@https.bugs.freebsd.org/bugzilla/> References: <bug-272706-29815@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D272706 --- Comment #5 from Andrew "RhodiumToad" Gierth <andrew@tao11.riddles.org.u= k> --- (In reply to Andrew "RhodiumToad" Gierth from comment #4) I've confirmed my analysis this far: vn_fullpath is being called with vp pointing to a physical filesystem vnode (i.e. not the nullfs node on the up= per layer, but the lower layer vnode backing it). Accordingly, since in general= the lower vnode is somewhere outside the jail root, the traverse of parent dirs never hits the process root directory, so the full path is shown. Most other uses of vn_fullpath will be starting from the upper-level vnode = (for example, because they just looked up a filename, or they have an open file, etc.), and in this case, the code seems to correctly traverse the upper lay= er and end at the process root dir. What I don't know is why the vm_object is apparently referencing the lower vnode rather than the upper one. --=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-272706-29815-0MZAXJG50E>