-
Notifications
You must be signed in to change notification settings - Fork 359
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
Early boot memory corruption sometimes causes chain crashes #2252
Comments
Some additional references:
|
This may be resolved with #2273 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The best repro case was found with #2251, preserved until fixed in https://github.com/alfreb/IncludeOS/tree/memory-ghost-repro . On that branch, starting at commit e81fb7c reproduce with
( Requires https://github.com/includeos/vmrunner )
Backtrace was fetched from gdb after building musl with debug symbols, and seeing the same issue:
The call to
strdup
in init_libc causes a crash in libc during malloc. Our heap should be ready at that time, since this is afterinit_heap
.Possible culprit:
enframe
asserts: https://git.musl-libc.org/cgit/musl/tree/src/malloc/mallocng/meta.h?h=v1.2.4#n205a_crash
https://git.musl-libc.org/cgit/musl/tree/src/exit/abort.c?h=v1.2.5#n27, after some system calls.alloc_group
calls enframe: https://git.musl-libc.org/cgit/musl/tree/src/malloc/mallocng/malloc.c#n267alloc_group
entry: https://git.musl-libc.org/cgit/musl/tree/src/malloc/mallocng/malloc.c#n174Note that I think this bug is also present on master, possibly the main reason for master not booting at the moment.
Things I've tried
The text was updated successfully, but these errors were encountered: