Re: kern/38968 (assertion "solocked2(so, so2)" failed at uipc_usrreq.c line 542)

[ad%NetBSD.org@localhost]

Synopsis: assertion "solocked2(so, so2)" failed at uipc_usrreq.c line 542

Responsible-Changed-From-To: kern-bug-people->ad
Responsible-Changed-By: ad%NetBSD.org@localhost
Responsible-Changed-When: Tue, 17 Jun 2008 09:15:35 +0000
Responsible-Changed-Why:
take


State-Changed-From-To: open->analyzed
State-Changed-By: ad%NetBSD.org@localhost
State-Changed-When: Tue, 17 Jun 2008 09:15:35 +0000
State-Changed-Why:
This is likely to be a broken assertion. During connection setup the remote 
end of the socket can briefly be locked by uipc_lock instead of the shared
per-connection lock. It's safe because the thread finishing the connection
setup holds uipc_lock at the time and is not going to send any data down
the pipe, or mess with the connection in any other significant way.