go, branch go1.11.8

[release-branch.go1.11] go1.11.8

2019-04-08T21:30:39Z

Change-Id: Ie15c45050f817213b3f5955dc98b48a6cf2a6317 Reviewed-on: https://go-review.googlesource.com/c/go/+/171148 Run-TryBot: Andrew Bonventre TryBot-Result: Gobot Gobot Reviewed-by: Brad Fitzpatrick

[release-branch.go1.11] doc: correct link in 1.11.8 notes

2019-04-08T20:29:20Z

Change-Id: I09e0c2720ec0a51dc73c24b4550a749448656025 Reviewed-on: https://go-review.googlesource.com/c/go/+/171143 Reviewed-by: Brad Fitzpatrick (cherry picked from commit 6f512c8d6696b288372c48c19058bbe9dcb79da0) Reviewed-on: https://go-review.googlesource.com/c/go/+/171146 Reviewed-by: Andrew Bonventre

[release-branch.go1.11] doc: document Go 1.11.8

2019-04-08T20:27:55Z

Change-Id: Ia06f7005f466e55a22c76bf2b47d74ee8eb77dd1 Reviewed-on: https://go-review.googlesource.com/c/go/+/171139 Reviewed-by: Brad Fitzpatrick (cherry picked from commit 739a78f2b8de3139ec253719d0a688c08b8e5324) Reviewed-on: https://go-review.googlesource.com/c/go/+/171142 Reviewed-by: Andrew Bonventre

[release-branch.go1.11] go1.11.7

2019-04-05T19:09:03Z

Change-Id: I14c2be9eedb5332d0b3a66029a86f7cb9e6091cc Reviewed-on: https://go-review.googlesource.com/c/go/+/170889 Run-TryBot: Andrew Bonventre Reviewed-by: Brad Fitzpatrick TryBot-Result: Gobot Gobot

[release-branch.go1.11] doc: document Go 1.11.7

2019-04-05T18:37:47Z

Change-Id: Iec5e69b3ea163f42234d3b73696427a7aa8732e3 Reviewed-on: https://go-review.googlesource.com/c/go/+/170884 Reviewed-by: Brad Fitzpatrick (cherry picked from commit e47ced78578c471cbcd34a7d6b223a71e84a46c8) Reviewed-on: https://go-review.googlesource.com/c/go/+/170887 Reviewed-by: Andrew Bonventre

[release-branch.go1.11] net: fix test after 8.8.8.8 changed its reverse DNS name

2019-03-27T18:47:39Z

Google's 8.8.8.8 DNS server used to reports its reverse DNS name as ending in ".google.com". Now it's "dns.google.". Change-Id: I7dd15f03239e5c3f202e471618ab867690cb4f9d Reviewed-on: https://go-review.googlesource.com/c/go/+/169679 Run-TryBot: Brad Fitzpatrick TryBot-Result: Gobot Gobot Reviewed-by: Dmitri Shuralyov (cherry picked from commit 3089d189569ed272eaf2bc6c4330e848a46e9999) Reviewed-on: https://go-review.googlesource.com/c/go/+/169718

[release-branch.go1.11] runtime: fix write barrier on wasm

2019-03-19T21:24:41Z

The current wasm write barrier implementation incorrectly implements the "deletion" part of the barrier. It correctly greys the new value of the pointer, but rather than also greying the old value of the pointer, it greys the object containing the slot (which, since the old value was just overwritten, is not going to contain the old value). This can lead to unmarked, reachable objects. Often, this is masked by other marking activity, but one specific sequence that can lead to an unmarked object because of this bug is: 1. Initially, GC is off, object A is reachable from just one pointer in the heap. 2. GC starts and scans the stack of goroutine G. 3. G copies the pointer to A on to its stack and overwrites the pointer to A in the heap. (Now A is reachable only from G's stack.) 4. GC finishes while A is still reachable from G's stack. With a functioning deletion barrier, step 3 causes A to be greyed. Without a functioning deletion barrier, nothing causes A to be greyed, so A will be freed even though it's still reachable from G's stack. This CL fixes the wasm write barrier. Fixes #30872. Change-Id: I8a74ee517facd3aa9ad606e5424bcf8f0d78e754 Reviewed-on: https://go-review.googlesource.com/c/go/+/167743 Run-TryBot: Austin Clements Reviewed-by: Cherry Zhang (cherry picked from commit d9db9e32e924a60bbfbb15cc0dd7cfaaf8a62a3b) Reviewed-on: https://go-review.googlesource.com/c/go/+/167746 Reviewed-by: Katie Hockman TryBot-Result: Gobot Gobot

[release-branch.go1.11] go1.11.6

2019-03-14T19:57:30Z

Change-Id: I944d7cb825b8791486446d78feae9eed0a5479c4 Reviewed-on: https://go-review.googlesource.com/c/go/+/167705 Run-TryBot: Andrew Bonventre TryBot-Result: Gobot Gobot Reviewed-by: Andrew Bonventre

[release-branch.go1.11] runtime: skip TestLockOSThreadAvoidsStatePropagation if one can't unshare

2019-03-14T19:33:12Z

This change splits a testprog out of TestLockOSThreadExit and makes it its own test. Then, this change makes the testprog exit prematurely with a special message if unshare fails with EPERM because not all of the builders allow the user to call the unshare syscall. Also, do some minor cleanup on the TestLockOSThread* tests. Fixes #29366. Change-Id: Id8a9f6c4b16e26af92ed2916b90b0249ba226dbe Reviewed-on: https://go-review.googlesource.com/c/155437 Run-TryBot: Michael Knyszek TryBot-Result: Gobot Gobot Reviewed-by: Brad Fitzpatrick (cherry picked from commit 429bae715876c69853bb63db1733f580e293c916) Reviewed-on: https://go-review.googlesource.com/c/go/+/167707 Run-TryBot: Andrew Bonventre Reviewed-by: Michael Knyszek

[release-branch.go1.11] doc: document Go 1.11.6

2019-03-14T18:11:32Z

Change-Id: I99832fa4f2c3ec28e2dad46cf7607f3766948031 Reviewed-on: https://go-review.googlesource.com/c/go/+/167698 Reviewed-by: Brad Fitzpatrick (cherry picked from commit d3bb45d9046bb7d12c4fc9cdaf122f36d001fd31) Reviewed-on: https://go-review.googlesource.com/c/go/+/167700