mirror of
https://github.com/golang/go
synced 2024-11-19 06:04:39 -07:00
7c1be45f58
One goroutine started up and was waiting in rw. Then another goroutine decided to close the pipe. The closing goroutine stalled calling p.io.Lock() in pipeHalf.close. (This happened in gccgo). If the closing goroutine had been able to set the ioclosed flag, it would have gone on to tell the runner that the pipe was closed, which would then send an EINVAL to the goroutine sleeping in rw. Unlocking p.io before sleeping in rw avoids the race. R=rsc, rsc1 CC=golang-dev https://golang.org/cl/1682048 |
||
---|---|---|
.. | ||
ioutil | ||
io_test.go | ||
io.go | ||
Makefile | ||
pipe_test.go | ||
pipe.go |