On Wed, Apr 24, 2002 at 06:36:19PM +0300, Ognyan Kulev wrote: > `pflocal/sock.c:sock_shutdown' can be called with both flags > SHUTDOWN_READ and SHUTDOWN_WRITE set (according to > `pflocal/socket.c:S_socket_shutdown'). When this happen the > `sock->lock' mutex is unlocked before calling `pipe_remove_reader' but > the next `if' statement (that checks for SHUTDOWN_WRITE) assumes that > `sock->lock' is locked. Is this a problem?
Yes, of course, the code was obviously wrong, and I think your fix is right. I tested it and checked it in. Thanks, Marcus -- `Rhubarb is no Egyptian god.' Debian http://www.debian.org [EMAIL PROTECTED] Marcus Brinkmann GNU http://www.gnu.org [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.marcus-brinkmann.de _______________________________________________ Bug-hurd mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-hurd
