[Bug 83761] [panic] vm-related panic: blst_radix_free: freeing free block

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=83761

Conrad Meyer <cem at freebsd.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|4.11-STABLE                 |CURRENT
                 CC|                            |cem at freebsd.org,
                   |                            |markj at FreeBSD.org
             Status|Closed                      |Open
         Resolution|FIXED                       |---

--- Comment #3 from Conrad Meyer <cem at freebsd.org> ---
I hit apparently the same stack and panic in FreeBSD-CURRENT 13.x, r340866.

panic: freeing free block
panic() at panic+0x3c/frame 0xfffffe00b4a59600
blst_meta_free() at blst_meta_free+0x12a/frame 0xfffffe00b4a59640
blst_meta_free() at blst_meta_free+0xd3/frame 0xfffffe00b4a59680
blst_meta_free() at blst_meta_free+0xd3/frame 0xfffffe00b4a596c0
blst_meta_free() at blst_meta_free+0xd3/frame 0xfffffe00b4a59700
blist_free() at blist_free+0x28/frame 0xfffffe00b4a59720
swp_pager_freeswapspace() at swp_pager_freeswapspace+0x102/frame
0xfffffe00b4a59740
swap_pager_dealloc() at swap_pager_dealloc+0x150/frame 0xfffffe00b4a59760
vm_object_terminate() at vm_object_terminate+0x58/frame 0xfffffe00b4a597a0
vm_object_deallocate() at vm_object_deallocate+0x588/frame 0xfffffe00b4a59820
vm_map_entry_deallocate() at vm_map_entry_deallocate+0x44/frame
0xfffffe00b4a59850
vm_map_process_deferred() at vm_map_process_deferred+0x3d/frame
0xfffffe00b4a59870
vm_map_remove() at vm_map_remove+0x48/frame 0xfffffe00b4a598a0
vmspace_exit() at vmspace_exit+0x1c4/frame 0xfffffe00b4a598f0
exit1() at exit1+0x4b5/frame 0xfffffe00b4a59970
sigexit() at sigexit+0x7f/frame 0xfffffe00b4a599a0
postsig() at postsig+0x31d/frame 0xfffffe00b4a59a70
ast() at ast+0x2e7/frame 0xfffffe00b4a59ab0
doreti_ast() at doreti_ast+0x1f/frame 0x7ffffffe0a70

For what it's worth, the system was out of memory at the time and the OOM
killer may have been involved.  Still, this is probably not an acceptable
outcome.  I have a core and can provide GDB information as-needed, but probably
not the core unredacted contents.

-- 
You are receiving this mail because:
You are the assignee for the bug.