okatu-loliandClaude Opus 4.7 0e9f874637 fix(net): synchronize Buf.Close with Write/Read to prevent nil-pointer panic ...

internal/net.Buf had Close() nilling the underlying bytes.Buffer without
taking the rw mutex, racing against concurrent Buf.Write() / Buf.Read()
calls. When the consumer of MultiReadCloser closes mid-download (via
downloader.interrupt()), in-flight chunk-download goroutines could
dereference a nil bytes.Buffer and panic the entire process — matching
the SIGSEGV stack reported in #9190 and one crash mode from #9537.

Make Close acquire the lock and have Read/Write return io.ErrClosedPipe
when the buffer has been nilled, instead of panicking.

Add a race-detector regression test (TestBufCloseWriteRace) that panics
many times without this fix and passes cleanly with it.

Co-Authored-By: Claude Opus 4.7 <[email protected]>

2026-05-29 09:37:13 +08:00

..

buf_race_test.go

fix(net): synchronize Buf.Close with Write/Read to prevent nil-pointer panic

2026-05-29 09:37:13 +08:00

request_test.go

chore: remove refs to deprecated io/ioutil (#5519)

2023-11-16 05:16:15 -06:00

request.go

fix(net): synchronize Buf.Close with Write/Read to prevent nil-pointer panic

2026-05-29 09:37:13 +08:00

serve.go

fix(net): unexpected write (#8291 close #8281)

2025-04-12 17:01:52 +08:00

util.go

refactor(net): pass request header (#8031 close #8008)

2025-03-01 18:35:34 +08:00