Re: kern/45093: kernel deadlock between TCP and UVM involving callouts

[Nick Hudson <skrll%netbsd.org@localhost>]

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

From: Nick Hudson <skrll%netbsd.org@localhost>
To: gnats-bugs%NetBSD.org@localhost, kern-bug-people%netbsd.org@localhost,
 gnats-admin%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost, bouyer%asim.lip6.fr@localhost
Cc: 
Subject: Re: kern/45093: kernel deadlock between TCP and UVM involving
 callouts
Date: Tue, 6 Jun 2017 08:41:38 +0100

 On 06/06/17 08:40, Manuel Bouyer wrote:
 > The following reply was made to PR kern/45093; it has been noted by GNATS.
 >
 > From: Manuel Bouyer <manuel.bouyer%lip6.fr@localhost>
 > To: gnats-bugs%netbsd.org@localhost
 > Cc: kern-bug-people%netbsd.org@localhost, gnats-admin%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost
 > Subject: Re: kern/45093: kernel deadlock between TCP and UVM involving
 >   callouts
 > Date: Tue, 6 Jun 2017 09:36:14 +0200
 >
 >   On Tue, Jun 06, 2017 at 02:55:00AM +0000, coypu%sdf.org@localhost wrote:
 >   > The following reply was made to PR kern/45093; it has been noted by GNATS.
 >   >
 >   > From: coypu%sdf.org@localhost
 >   > To: gnats-bugs%netbsd.org@localhost
 >   > Cc:
 >   > Subject: Re: kern/45093: kernel deadlock between TCP and UVM involving
 >   >  callouts
 >   > Date: Tue, 6 Jun 2017 02:51:10 +0000
 >   >
 >   >  Is there still an issue?
 >   
 >   no this specific path should have been fixed by my commit.
 >   
 >   But I don't know if there are other places sleeping with the
 >   softnet_lock held ...
 >   
 There are several... NET_MPSAFE needs to be completed/enabled to remove 
 the ones I've seen.
 
 Nick