runtime, x/sys/unix: Connectx is broken on darwin/amd64 [1.23 backport]

[randall77]

@randall77 requested issue #71302 to be considered for backport to the next 1.23 minor release.

Ok, that's good. I'll get that CL in soon.

I think the remaining question is, should we backport?
In favor:

1. This could cause really weird behavior and/or corruption on darwin/amd64. There is only one stdlib call affected (syscall/Getnameinfo), but several in x.sys (Connectx for freebsd, mmap for netbsd, dragonfly).
2. darwin/amd64 is a first-class port.

In opposition:

1. This has always been broken (since introduced in late 2022). It is not a regression from 1.24.
2. Only the Connectx failure has been noticed.

I'm leaning towards backporting. The fix is pretty simple and the unfixed behavior is very hard to debug and/or work around.

@gopherbot please open backport issues

[gopherbot]

Change https://go.dev/cl/666015 mentions this issue: [release-branch.go1.23] runtime: fix 9-arg syscall on darwin/amd64

[gopherbot]

Closed by merging CL 666015 (commit 8ff45d1) to release-branch.go1.23.

[ldemailly]

so this fix caused #73617, right ? and will need to be further patched - are we getting 1.23.10 soon then?
what's the advice on whether to upgrade to 1.23.9 or not from 1.23.8 ?

[randall77]

I think you have a wrong issue number. This one has nothing to do with dlopen.
I think you're looking for #73091.

[ldemailly]

Opsa my bad, saw assembly and the one platform that broke and thought that must have been it, sorry (and had 50% chance yet managed to guess wrong)