New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
syscall: SysProcAttr{ NoInheritHandles: true } broken in 1.17 on Windows [1.17 backport] #48075
Labels
Milestone
Comments
gopherbot
added
the
CherryPickCandidate
Used during the release process for point releases
label
Aug 30, 2021
Change https://golang.org/cl/350416 mentions this issue: |
CC @JohanKnutzen in case you wanted to track its inclusion in 1.17.y. |
@zx2c4 Excellent. Thanks for the patch. Looking forward to this being rolled out. |
heschi
added
CherryPickApproved
Used during the release process for point releases
and removed
CherryPickCandidate
Used during the release process for point releases
labels
Oct 6, 2021
Closed by merging 11b64b4 to release-branch.go1.17. |
gopherbot
pushed a commit
that referenced
this issue
Oct 25, 2021
…hen NoInheritHandles is true If NoInheritHandles is passed, then we shouldn't attempt to do anything with handle lists. Otherwise CreateProcess fails with invalid param, because it's being told both to not inherit handles and to inherit certain handles. This commit fixes that by using the same logic for handle lists as it does for enabling or disabling handle inheritance. It also adds a test to make sure this doesn't regress again. Updates #48040 Fixes #48075 Change-Id: I507261baeec263091738ab90157a991d917dc92f Reviewed-on: https://go-review.googlesource.com/c/go/+/350416 Trust: Jason A. Donenfeld <Jason@zx2c4.com> Run-TryBot: Jason A. Donenfeld <Jason@zx2c4.com> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Patrik Nyblom <pnyb@google.com>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
@bcmills requested issue #48040 to be considered for backport to the next 1.17 minor release.
The text was updated successfully, but these errors were encountered: