Alex Brainman c37647fc3a internal/poll: do not call SetFileCompletionNotificationModes if it is broken ... Current code assumes that SetFileCompletionNotificationModes is safe to call even if we know that it is not safe to use FILE_SKIP_COMPLETION_PORT_ON_SUCCESS flag. It appears (see issue #22149), SetFileCompletionNotificationModes crashes when we call it without FILE_SKIP_COMPLETION_PORT_ON_SUCCESS flag. Do not call SetFileCompletionNotificationModes in that situation. We are allowed to do that, because SetFileCompletionNotificationModes is just an optimisation. Fixes #22149 Change-Id: I0ad3aff4eabd8c27739417a62c286b1819ae166a Reviewed-on: https://go-review.googlesource.com/69870 Reviewed-by: Ian Lance Taylor <iant@golang.org>		2017-10-12 07:12:36 +00:00
..
cpu	internal/cpu: add support for x86 FMA cpu feature detection	2017-09-11 05:20:01 +00:00
nettrace
poll	internal/poll: do not call SetFileCompletionNotificationModes if it is broken	2017-10-12 07:12:36 +00:00
race	testing: mark tests and benchmarks failed if a race occurs during execution	2016-11-03 18:19:49 +00:00
singleflight
syscall	path/filepath: re-implement windows EvalSymlinks	2017-10-05 04:16:00 +00:00
testenv	internal/testenv: take testing.TB instead of *testing.T in MustHave* and SkipFlaky*	2017-09-19 23:34:28 +00:00
trace	all: revert "all: prefer strings.LastIndexByte over strings.LastIndex"	2017-10-05 23:19:42 +00:00