syscall.Getpagesize returns wrong page size on aarch64

Also noted here: https://github.com/vielmetti/go-pagesize-test/issues/4

A backport of this fix, to 1.7: https://github.com/golang/go/issues/10180#issuecomment-277004348

I had a quick look at this and it doesn't backport cleanly to 1.6. Can I ask why you are interested in this? I have a PPA (and soon a snap) with newer versions of Go and using those is probably easier than backporting this change...

If Go 1.8 would be available via a PPA that would obviate the need for a fix to Go 1.6.

@mwhudson - when you are ready to test the PPA I am very interested in giving it a spin on a dedicated ARMv8 test server.

https://code.launchpad.net/~gophers/+archive/ubuntu/archive/+packages has
1.8~rc3 already, will have 1.8 when that's done. I could add the patch to
the 1.7 in that PPA too (but not today)

On 11 February 2017 at 05:38, Edward Vielmetti <email address hidden>
wrote:

> @mwhudson - when you are ready to test the PPA I am very interested in
> giving it a spin on a dedicated ARMv8 test server.
>
> --
> You received this bug notification because you are subscribed to golang
> in Ubuntu.
> https://bugs.launchpad.net/bugs/1661222
>
> Title:
> syscall.Getpagesize returns wrong page size on aarch64
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/golang/+bug/
> 1661222/+subscriptions
>

Thanks Michael. I see that 1.8 release is out, and will look forward to seeing that when it's ready on your archive.

1.8 final is in my PPA now.

We only ship kernels with one page size on arm64. While backporting the *correct* (dynamic query) fix might be a bit too painful, we should at least consider changing the static value to be "usually correct" (ie: 4k).

With the changes staged at ppa:mwhudson/devirt (1.6.2-0ubuntu5~16.04.4~ppa1):

dannf@d05-3:~/go-pagesize-test$ make
bats go-pagesize-test.bats
 ✓ go reports correct pagesize

1 test, 0 failures

Hello Edward, or anyone else affected,

Accepted golang-1.6 into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/golang-1.6/1.6.2-0ubuntu5~16.04.4 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

The test I ran was with

`golang-1.6/xenial-proposed,now 1.6.2-0ubuntu5~16.04.4 all [installed,automatic]`

on an arm64 system. The test code is at

https://github.com/vielmetti/go-pagesize-test

With this version, I get the following results on a Cavium ThunderX based Packet Type 2A system:

```
# make
bats go-pagesize-test.bats
 ✓ go reports correct pagesize

1 test, 0 failures
```

This bug was fixed in the package golang-1.6 - 1.6.2-0ubuntu5~16.04.4

---------------
golang-1.6 (1.6.2-0ubuntu5~16.04.4) xenial; urgency=medium

  * Add d/patches/0004-arm64-better-guessed-page-size.patch to fix problems
    seen with docker on arm64 systems. (LP: #1661222)

 -- Michael Hudson-Doyle <email address hidden> Wed, 19 Jul 2017 10:56:27 +1200

The verification of the Stable Release Update for golang-1.6 has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.