-
Notifications
You must be signed in to change notification settings - Fork 17.3k
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
runtime: logget fails log entry on Plan 9 #9846
Comments
/cc @RLH |
/cc me |
Working theory: a15818f removed the zeroing of workbufs after they were allocated with persistentAlloc. This is fine on POSIX systems that use anonymous mmap to get memory for persistentAlloc, but Plan9 uses sbrk. I'm not sure how sbrk works on Plan9, but if something did a negative sbrk (maybe within a page), followed by the sbrk for this persistentAlloc, it could return non-zeroed memory. |
I had missed that sbrk was our own implementation and not a syscall on Plan 9. But I was right that sysAlloc can return non-zeroed memory on Plan 9 because sysFree has an optimization to roll back the brk without zeroing it, causing the next sysAlloc to return potentially non-zeroed memory. |
Since CL 3972, the TestTraceStress test from the runtime/pprof package is intermittently failing.
http://build.golang.org/log/c809f02dcf6b0b387c548cca1d0dc2b4568e8e35
The text was updated successfully, but these errors were encountered: