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

[Manuel Bouyer <bouyer%antioche.eu.org@localhost>]

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

From: Manuel Bouyer <bouyer%antioche.eu.org@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: hannken%netbsd.org@localhost, gnats-admin%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost,
        manu%netbsd.org@localhost, gson%gson.org@localhost
Subject: Re: kern/53624 (dom0 freeze on domU exit) is still there
Date: Wed, 9 Oct 2019 15:31:42 +0200

 On Fri, Oct 04, 2019 at 09:45:01AM +0000, J. Hannken-Illjes wrote:
 > 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: Fri, 4 Oct 2019 11:40:54 +0200
 > 
 >  --Apple-Mail=_788E5721-9DB9-4F79-AE00-7266B8F7D8D0
 >  Content-Transfer-Encoding: 7bit
 >  Content-Type: text/plain;
 >  	charset=us-ascii
 >  
 >  Looks like we have to use fstrans_start_lazy() for VOP_STRATEGY() too
 >  as it usually calls itself on the file system holding "/dev".
 >  
 >  The attached diff could help, please give it a try.
 
 Looks good, I have completed 2 rounds of tests without problems.
 
 -- 
 Manuel Bouyer <bouyer%antioche.eu.org@localhost>
      NetBSD: 26 ans d'experience feront toujours la difference
 --