Re: kern/53624 (dom0 freeze on domU exit) is still there

["J. Hannken-Illjes" <hannken%eis.cs.tu-bs.de@localhost>]

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

From: "J. Hannken-Illjes" <hannken%eis.cs.tu-bs.de@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: kern/53624 (dom0 freeze on domU exit) is still there
Date: Thu, 3 Oct 2019 18:09:59 +0200

 --Apple-Mail=_9D0BB28E-3676-4CD0-ADE7-D400968E0442
 Content-Transfer-Encoding: quoted-printable
 Content-Type: text/plain;
 	charset=us-ascii
 
 
 > On 3. Oct 2019, at 11:05, J. Hannken-Illjes <hannken%eis.cs.tu-bs.de@localhost> =
 wrote:
 <snip>
 > - the traces of the two vnd threads in "fstchg" don't contain
 >   obvious accesses to "/"
 
 Problem understood, VOP_GETPAGES()/VOP_PUTPAGES() do:
 
 VOP_BMAP(vp, lbn, &devvp, &blkno, &run);
 VOP_STRATEGY(devvp, bp);
 
 While vp resides on "/domains", devvp (the device it was
 mounted from) resides on "/".
 
 --
 J. Hannken-Illjes - hannken%eis.cs.tu-bs.de@localhost - TU Braunschweig
 
 
 --Apple-Mail=_9D0BB28E-3676-4CD0-ADE7-D400968E0442
 Content-Transfer-Encoding: 7bit
 Content-Disposition: attachment;
 	filename=signature.asc
 Content-Type: application/pgp-signature;
 	name=signature.asc
 Content-Description: Message signed with OpenPGP
 
 -----BEGIN PGP SIGNATURE-----
 
 iQEzBAEBCAAdFiEE2BL3ha7Xao4WUZVYKoaVJdNr+uEFAl2WHVcACgkQKoaVJdNr
 +uEU1wf/aHq5fUnJdWYfaRRHSXhmqYtMa2fjS3bcOEkVCJXv7Zgj5Omsl2rNNFN8
 CQ/A024LvGAsBL4RgFwofrAPbk/KBx/B+E3m40rBZnV0DMgijBZBQnQSO5CgG3X1
 x7QWyp95K0+0lnKLGY8pZ231pOeZR+JhSiJTOB8UwJyAqU4K8FrgnIUVUv8ePchp
 076bPyALg3Sv2dGbNrkti53RI2KxM/rrvykw0kRcnnV+s4yckfMknU1XM6KeJuyX
 0j6ZAO1VXDBW7sYYWK2T3ZmFJLl4DYendMHDlL2/Tzcwgu1RclqAIndAMw+vFezB
 xchhPwWm93Pnz6t5WAO3cgFykVPirA==
 =KgS5
 -----END PGP SIGNATURE-----
 
 --Apple-Mail=_9D0BB28E-3676-4CD0-ADE7-D400968E0442--