syscall: incorrect length of abstract Unix domain socket paths beginning with null character #63579
Labels
compiler/runtime
Issues related to the Go compiler and/or runtime.
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
https://go.dev/play/p/QzrhBGKYhJc
What did you expect to see?
What did you see instead?
In the syscall file there is code that special-cases handling of unix socket names beginning with
@
by removing the trailing NUL character but it does not do the same for unix socket names starting with the NUL character.It seems obvious to me that this is just a simple oversight and the fix is very simple. Lemme just make a PR...
The text was updated successfully, but these errors were encountered: