mmap on wsl is ignoring RLIMIT_AS?

[KiYugadgeter]

Windows10 1803 build:17134

I tried build golang from source.
But it has failed on ubuntu 18.04 on WSL.
This error is caused by wrong mmap behavior.

--- FAIL: TestRlimitAs (0.00s)
syscall_linux_test.go:180: Mmap: unexpectedly suceeded after setting RLIMIT_AS

mmap of WSL seems like does not respect RESOURCE_AS limitation.

[KiYugadgeter]

My Version is : Windows10 1803 build:17134.228

I have put code here:
https://gist.github.com/KiYugadgeter/a26aabcadb8fffa8fbdda2c75a44cd38

[therealkenc]

Fail is here. Yes, please fill out TEMPLATE.md (with special attention to the last sentence of the first paragraph). Most important being an strace capturing the setrlimit() and mmap() bits for that part of syscall_linux_test.go. [ed: thanks for the test code our posts crossed]

But in this instance, this is essentially dupe #2526. The strace log is almost certainly going to show setrlimit() and mmap() succeeding because (we can reasonably assume) RLIMIT_AS is stubbed. So, it will boil down to stating the use case, namely identifying the "killer golang applications with widespread adoption" that a stubbed RLIMIT_AS is blocking.

Snippet of test golang test code at issue:

	// RLIMIT_AS was set to the page size, so mmap()'ing twice the page size
	// should fail. See 'man 2 getrlimit'.
	_, err = unix.Mmap(-1, 0, 2*unix.Getpagesize(), unix.PROT_NONE, unix.MAP_ANON|unix.MAP_PRIVATE)
	if err == nil {
		t.Fatal("Mmap: unexpectedly suceeded after setting RLIMIT_AS")
	}

[KiYugadgeter]

I have tried strace some times but it does not done despite I waited several hours.

[KiYugadgeter]

This bug is fixed on beta?

[gnaggnoyil]

Can confirm setrlimit(RLIMIT_AS) still fails silently on WSL1 environment, different with real linux environment even if the linux distribution are the same. I'm using WSL1 on Windows 10 22H2 19045.2251.

https://gist.github.com/gnaggnoyil/cda2ff5748beab3c519467eba66d80da

[microsoft-github-policy-service]

This issue has been automatically closed since it has not had any activity for the past year. If you're still experiencing this issue please re-file this as a new issue or feature request.

Thank you!