Re: kern/51412: Syscall I/O race condition leads to deadlock and lost interrupts

[Robert Elz <kre%munnari.OZ.AU@localhost>]

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

From: Robert Elz <kre%munnari.OZ.AU@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: Paul Goyette <paul%whooppee.com@localhost>
Subject: Re: kern/51412: Syscall I/O race condition leads to deadlock and lost interrupts
Date: Tue, 06 Sep 2016 07:58:04 +0700

     Date:        Mon,  5 Sep 2016 18:55:01 +0000 (UTC)
     From:        David Holland <dholland-bugs%netbsd.org@localhost>
     Message-ID:  <20160905185501.8A7777A283%mollari.NetBSD.org@localhost>
 
 
   |   >  What I do know is that using one and/or the other command can influence the
   |   >  execution of the other. 
   |  
   |  This is odd, but we'll certainly look into it.
 
 I wonder if this is related to the "blast from the past" message Paul
 just posted about (on tech-kern).   Locking problems with sysctl() seem
 to be related to both ... 
 
 See:
 	https://mail-index.netbsd.org/current-users/2015/10/27/msg028285.html
 	https://mail-index.netbsd.org/tech-kern/2016/09/05/msg021028.html
 	https://mail-index.netbsd.org/tech-kern/2016/09/05/msg021029.html
 
 kre