My system received the following warning and restarted abnormally.
------------[ cut here ]------------
list_del corruption. next->prev should be ffffe3914d5485c8, but was ffff9e648e9d6030
WARNING: CPU: 71 PID: 2333951 at lib/list_debug.c:56 __list_del_entry_valid+0x8a/0x90
RIP: 0010:__list_del_entry_valid+0x8a/0x90
Call Trace:
isolate_lru_pages.isra.65+0x126/0x5f0
shrink_active_list+0xcf/0x5a0
shrink_node_memcg+0x231/0x770
shrink_node+0xcf/0x410
do_try_to_free_pages+0xc9/0x370
try_to_free_pages+0xf0/0x1b0
__alloc_pages_slowpath+0x392/0xd40
__alloc_pages_nodemask+0x277/0x2a0
__do_page_cache_readahead+0xb1/0x1d0
filemap_fault+0x27b/0x770
__xfs_filemap_fault+0x72/0x200 [xfs]
__do_fault+0x31/0xc0
do_fault+0x12e/0x490
__handle_mm_fault+0x621/0x6a0
handle_mm_fault+0xdc/0x260
__do_page_fault+0x2ba/0x4d0
do_page_fault+0x31/0x130
page_fault+0x1e/0x30
---[ end trace c612dce95fbdb099 ]---
------------[ cut here ]------------
list_del corruption. prev->next should be ffffe391404b8fc8, but was ffffe3915701de88
WARNING: CPU: 7 PID: 711 at lib/list_debug.c:53 __list_del_entry_valid+0x79/0x90
RIP: 0010:__list_del_entry_valid+0x79/0x90
Call Trace:
isolate_lru_pages.isra.65+0x126/0x5f0
shrink_inactive_list+0x13e/0x6b0
shrink_node_memcg+0x365/0x770
shrink_node+0xcf/0x410
kswapd+0x2b6/0x6f0
kthread+0x113/0x130
ret_from_fork+0x35/0x40
---[ end trace c612dce95fbdb09a ]---
------------[ cut here ]------------
kernel BUG at mm/vmscan.c:1734!
invalid opcode: 0000 [#1] SMP NOPTI
RIP: 0010:isolate_lru_pages.isra.65+0x5e4/0x5f0
Call Trace:
shrink_inactive_list+0x13e/0x6b0
shrink_node_memcg+0x365/0x770
shrink_node+0xcf/0x410
do_try_to_free_pages+0xc9/0x370
try_to_free_pages+0xf0/0x1b0
__alloc_pages_slowpath+0x392/0xd40
__alloc_pages_nodemask+0x277/0x2a0
__do_page_cache_readahead+0xb1/0x1d0
filemap_fault+0x27b/0x770
__xfs_filemap_fault+0x72/0x200 [xfs]
__do_fault+0x31/0xc0
do_fault+0x12e/0x490
__handle_mm_fault+0x621/0x6a0
handle_mm_fault+0xdc/0x260
__do_page_fault+0x2ba/0x4d0
do_page_fault+0x31/0x130
page_fault+0x1e/0x30
The system restarted abnormally and generated a kernel dump file. After analyzing it, I couldn’t find the cause, but I guessed it was related to concurrent access.
The kernel version is based on 4.19.90.
Because the version is relatively low, so I want to have this problem fixed in high version? Is there a fix for it?
Thanks.
2