Date: Sun, 27 Sep 2020 14:56:16 -0500 From: Kyle Evans <kevans@freebsd.org> To: Yuri <yuri@rawbw.com> Cc: Freebsd hackers list <freebsd-hackers@freebsd.org> Subject: Re: Is it possible to exit the chroot(2) environment? Message-ID: <CACNAnaG_u1aVRJpKeb9n0rK4UqRRZDGBt7i=iRtPf-7kxqYQBw@mail.gmail.com> In-Reply-To: <a488f94a-6efc-27f3-d0a4-489f6f99772d@rawbw.com> References: <b6412618-02ec-1dbd-f474-b4412d7b774b@rawbw.com> <CANCZdfqJ14-Cpvi9%2Bd%2BHRgWbHk7vDUNNOKLUVOC9iBUqZKX=Pw@mail.gmail.com> <CACNAnaFVg2yZnWbfC=MmPfQ==XZYssHFuz%2BCjz%2B67TkZ108qRA@mail.gmail.com> <CACNAnaF-psLeTzwk=HygP4ESEynRyR-m62T1FAjw=ON6J2PVTg@mail.gmail.com> <a488f94a-6efc-27f3-d0a4-489f6f99772d@rawbw.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Sep 27, 2020 at 2:47 PM Yuri <yuri@rawbw.com> wrote: > > On 2020-09-27 12:42, Kyle Evans wrote: > > I think the original report needs a ktrace to narrow down what's > > really going on... > > > https://people.freebsd.org/~yuri/rpm-ktrace-dump-chroot-fails.txt > Yup, that's pretty definitive: 69691 python3.7 CALL chroot(0x8026e6ad2) 69691 python3.7 NAMI "." 69691 python3.7 RET chroot -1 errno 1 Operation not permitted Note the explanation of EPERM: [EPERM] The effective user ID is not the super-user, or one or more filedescriptors are open directories. For the former half, a chroot in the very same python3.7 exec succeeded, so it must not be that. Try setting kern.chroot_allow_open_directories to some value that isn't 0 or 1.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CACNAnaG_u1aVRJpKeb9n0rK4UqRRZDGBt7i=iRtPf-7kxqYQBw>