Date: Sat, 18 Nov 2017 11:58:03 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 223327] dhclient: close the pidfile before calling chroot(2) Message-ID: <bug-223327-8-x7FlA7vp0k@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-223327-8@https.bugs.freebsd.org/bugzilla/> References: <bug-223327-8@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=223327 Kristof Provost <kp@freebsd.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |cem@freebsd.org, | |kp@freebsd.org, | |markj@FreeBSD.org, | |oshogbo@freebsd.org --- Comment #1 from Kristof Provost <kp@freebsd.org> --- Hmm. This is quite interesting. I think the problem started with r322369 which changed libutil / pidfile_open() to keep the directory fd (rather than the pidfile fd) so it could unlink the pidfile in capability mode. That appears to conflict with chroot now, because you can't chroot if you've got a directory fd open to somewhere outside the new root. I don't think this patch is right, because it'll break the pidfile_remove() in routehandler(). I'm not at all sure how this should be fixed though. -- 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-223327-8-x7FlA7vp0k>