-
Notifications
You must be signed in to change notification settings - Fork 18k
syscall: SyscallN always escapes the variadic argument [1.22 backport] #70201
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
Comments
I'm not sure this warrants a backport. Risk of someone switching to a deprecated API doesn't constitute "serious problem with no workaround". |
The issue with the deprecated APIs (for example syscall.Syscall is that it is easy to set the wrong |
We decided not to backport because it isn't a regression, and the problem will be solved with the 1.24 release. |
@ianlancetaylor points out that this is a regression-in-waiting and blocks progress on x/sys/windows, so, reopen for consideration next week. |
Change https://go.dev/cl/630215 mentions this issue: |
syscall.SyscallN is implemented by runtime.syscall_syscalln, which makes sure that the variadic argument doesn't escape. There is no need to worry about the lifetime of the elements of the variadic argument, as the compiler will keep them live until the function returns. For #70197 Fixes #70201 Change-Id: I12991f0be12062eea68f2b103fa0a794c1b527eb Reviewed-on: https://go-review.googlesource.com/c/go/+/625297 Reviewed-by: Ian Lance Taylor <[email protected]> Reviewed-by: Alex Brainman <[email protected]> Reviewed-by: David Chase <[email protected]> LUCI-TryBot-Result: Go LUCI <[email protected]> (cherry picked from commit 7fff741) Reviewed-on: https://go-review.googlesource.com/c/go/+/630215 Reviewed-by: Dmitri Shuralyov <[email protected]> Reviewed-by: Quim Muntal <[email protected]> Reviewed-by: Dmitri Shuralyov <[email protected]> Auto-Submit: Ian Lance Taylor <[email protected]>
@qmuntal requested issue #70197 to be considered for backport to the next 1.22 minor release.
The text was updated successfully, but these errors were encountered: