Not protecting globrunqputbatch can lead to very bad things, since manipulating the global runq is protected by sched.lock. In particular, we've seen nil g pointers in the global runq as well as general corruption of the global runq field in production.
The fix is straightforward and I'll upload it shortly. This problem is new in Go 1.15.
The text was updated successfully, but these errors were encountered: