It’s the kernel. Nothing a user space library can do should ever be able to call this.
replyJust happens to be that the musl code is able to hit this and other code isn’t for some reason.
> It’s the kernel. Nothing a user space library can do should ever be able to call this.
replyI don't follow. An application might see this kind of crash if it has a bug causing it to access a page while another thread is mapping or unmapping that page. That would be a bug in mallocng, musl or ripgrep. Or, as someone else mentioned, it could be bug in the processor's virtual memory logic that has the same effect. Why do you say it can only be a kernel bug?
It got traced to a race condition in munmap() in the kernel. The inefficient musl allocator simply triggers it more easily.
replyIt got arm-waved to a race condition in munmap(). Claude (or a distill of Claude) didn't identify a race, it just convinced itself that was the cause.
replyUser code calls kernel code all the time - just not by its address.
replyI mean, we are deep into reading tea leaves at this point, but what it seems to have identified is the source file that changed such that this issue can now occur. My gut instinct is that the changed code is still valid and correct, but it exercises the hardware in a different or a more intense way.
reply