Re: bin/60493: autofs does not handle chroot

The following reply was made to PR bin/60493; it has been noted by GNATS.

From: "Simon J. Gerraty" <[email protected]>
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: bin/60493: autofs does not handle chroot
Date: Fri, 07 Aug 2026 18:19:43 -0700

 On Sat, 8 Aug 2026 00:30:01 +0000 (UTC), "Simon J. Gerraty via gnats" writ=
 es:
 > >Updated patch -- this one initializes chrootpath as the somewhat
 > >sharp-edged getcwd_common expects, so it doesn't lead to immediate
 > >null pointer dereference.
 > =
 
 > Thanks, I'll have to think about how to test this, since no
 > longer running zfs with the ramdisk trick.
 
 Ok not sure how valid this is...
 
 I stopped auto*mount*
 I built and loaded the new autofs module.
 restarted auto*mount* and confirmed autofs still worked.
 
 I stopped auto*mount*
 and created a quick and dirty chroot
 
 /h/tmp/chroot/ with a full copy of /etc
 and just enough of /lib and /libexec to run =
 
 cat /h/tmp/chroot/tmp/tit.sh
 #/bin/sh
 
 /etc/rc.d/autounmountd start
 /etc/rc.d/automountd start
 /etc/rc.d/automount start
 
 df -h /homes/sjg/tmp
 
 when I ran that it hung at df
 dmesg says
 
 [ 511376.695498] WARNING: autofs_trigger_one: cv_wait_sig for /h/tmp/chroo=
 t/homes/ failed with error -3