Miaohe Lin
52ccdde16b
mm/hugetlb: fix DEBUG_LOCKS_WARN_ON(1) when dissolve_free_hugetlb_folio()
...
When I did memory failure tests recently, below warning occurs:
DEBUG_LOCKS_WARN_ON(1)
WARNING: CPU: 8 PID: 1011 at kernel/locking/lockdep.c:232 __lock_acquire+0xccb/0x1ca0
Modules linked in: mce_inject hwpoison_inject
CPU: 8 PID: 1011 Comm: bash Kdump: loaded Not tainted 6.9.0-rc3-next-20240410-00012-gdb69f219f4be #3
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014
RIP: 0010:__lock_acquire+0xccb/0x1ca0
RSP: 0018:ffffa7a1c7fe3bd0 EFLAGS: 00000082
RAX: 0000000000000000 RBX: eb851eb853975fcf RCX: ffffa1ce5fc1c9c8
RDX: 00000000ffffffd8 RSI: 0000000000000027 RDI: ffffa1ce5fc1c9c0
RBP: ffffa1c6865d3280 R08: ffffffffb0f570a8 R09: 0000000000009ffb
R10: 0000000000000286 R11: ffffffffb0f2ad50 R12: ffffa1c6865d3d10
R13: ffffa1c6865d3c70 R14: 0000000000000000 R15: 0000000000000004
FS: 00007ff9f32aa740(0000) GS:ffffa1ce5fc00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ff9f3134ba0 CR3: 00000008484e4000 CR4: 00000000000006f0
Call Trace:
<TASK>
lock_acquire+0xbe/0x2d0
_raw_spin_lock_irqsave+0x3a/0x60
hugepage_subpool_put_pages.part.0+0xe/0xc0
free_huge_folio+0x253/0x3f0
dissolve_free_huge_page+0x147/0x210
__page_handle_poison+0x9/0x70
memory_failure+0x4e6/0x8c0
hard_offline_page_store+0x55/0xa0
kernfs_fop_write_iter+0x12c/0x1d0
vfs_write+0x380/0x540
ksys_write+0x64/0xe0
do_syscall_64+0xbc/0x1d0
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7ff9f3114887
RSP: 002b:00007ffecbacb458 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 000000000000000c RCX: 00007ff9f3114887
RDX: 000000000000000c RSI: 0000564494164e10 RDI: 0000000000000001
RBP: 0000564494164e10 R08: 00007ff9f31d1460 R09: 000000007fffffff
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000000000c
R13: 00007ff9f321b780 R14: 00007ff9f3217600 R15: 00007ff9f3216a00
</TASK>
Kernel panic - not syncing: kernel: panic_on_warn set ...
CPU: 8 PID: 1011 Comm: bash Kdump: loaded Not tainted 6.9.0-rc3-next-20240410-00012-gdb69f219f4be #3
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014
Call Trace:
<TASK>
panic+0x326/0x350
check_panic_on_warn+0x4f/0x50
__warn+0x98/0x190
report_bug+0x18e/0x1a0
handle_bug+0x3d/0x70
exc_invalid_op+0x18/0x70
asm_exc_invalid_op+0x1a/0x20
RIP: 0010:__lock_acquire+0xccb/0x1ca0
RSP: 0018:ffffa7a1c7fe3bd0 EFLAGS: 00000082
RAX: 0000000000000000 RBX: eb851eb853975fcf RCX: ffffa1ce5fc1c9c8
RDX: 00000000ffffffd8 RSI: 0000000000000027 RDI: ffffa1ce5fc1c9c0
RBP: ffffa1c6865d3280 R08: ffffffffb0f570a8 R09: 0000000000009ffb
R10: 0000000000000286 R11: ffffffffb0f2ad50 R12: ffffa1c6865d3d10
R13: ffffa1c6865d3c70 R14: 0000000000000000 R15: 0000000000000004
lock_acquire+0xbe/0x2d0
_raw_spin_lock_irqsave+0x3a/0x60
hugepage_subpool_put_pages.part.0+0xe/0xc0
free_huge_folio+0x253/0x3f0
dissolve_free_huge_page+0x147/0x210
__page_handle_poison+0x9/0x70
memory_failure+0x4e6/0x8c0
hard_offline_page_store+0x55/0xa0
kernfs_fop_write_iter+0x12c/0x1d0
vfs_write+0x380/0x540
ksys_write+0x64/0xe0
do_syscall_64+0xbc/0x1d0
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7ff9f3114887
RSP: 002b:00007ffecbacb458 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 000000000000000c RCX: 00007ff9f3114887
RDX: 000000000000000c RSI: 0000564494164e10 RDI: 0000000000000001
RBP: 0000564494164e10 R08: 00007ff9f31d1460 R09: 000000007fffffff
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000000000c
R13: 00007ff9f321b780 R14: 00007ff9f3217600 R15: 00007ff9f3216a00
</TASK>
After git bisecting and digging into the code, I believe the root cause is
that _deferred_list field of folio is unioned with _hugetlb_subpool field.
In __update_and_free_hugetlb_folio(), folio->_deferred_list is
initialized leading to corrupted folio->_hugetlb_subpool when folio is
hugetlb. Later free_huge_folio() will use _hugetlb_subpool and above
warning happens.
But it is assumed hugetlb flag must have been cleared when calling
folio_put() in update_and_free_hugetlb_folio(). This assumption is broken
due to below race:
CPU1 CPU2
dissolve_free_huge_page update_and_free_pages_bulk
update_and_free_hugetlb_folio hugetlb_vmemmap_restore_folios
folio_clear_hugetlb_vmemmap_optimized
clear_flag = folio_test_hugetlb_vmemmap_optimized
if (clear_flag) <-- False, it's already cleared.
__folio_clear_hugetlb(folio) <-- Hugetlb is not cleared.
folio_put
free_huge_folio <-- free_the_page is expected.
list_for_each_entry()
__folio_clear_hugetlb <-- Too late.
Fix this issue by checking whether folio is hugetlb directly instead of
checking clear_flag to close the race window.
Link: https://lkml.kernel.org/r/20240419085819.1901645-1-linmiaohe@huawei.com
Fixes: 32c877191e02 ("hugetlb: do not clear hugetlb dtor until allocating vmemmap")
Signed-off-by: Miaohe Lin <linmiaohe@huawei.com>
Reviewed-by: Oscar Salvador <osalvador@suse.de>
Cc: <stable@vger.kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
2024-04-25 10:07:27 -07:00
..
2024-03-04 17:01:18 -08:00
2024-03-14 17:43:30 -07:00
2023-12-05 11:17:58 +01:00
2024-02-22 10:24:41 -08:00
2024-03-11 09:38:17 -07:00
2022-08-02 12:34:03 -04:00
2023-10-25 16:47:13 -07:00
2022-09-11 20:25:50 -07:00
2024-02-22 10:24:57 -08:00
2024-02-22 10:24:57 -08:00
2024-02-22 10:24:57 -08:00
2024-03-14 17:43:30 -07:00
2024-01-08 15:27:15 -08:00
2024-02-23 17:27:13 -08:00
2024-03-06 13:04:18 -08:00
2023-04-05 19:42:38 -07:00
2023-12-05 11:17:58 +01:00
2023-06-09 16:25:56 -07:00
2023-06-23 16:59:31 -07:00
2023-06-09 16:25:23 -07:00
2022-11-22 18:50:44 -08:00
2024-03-26 11:07:20 -07:00
2023-12-29 11:58:27 -08:00
2023-06-23 16:58:19 -07:00
2022-11-08 17:37:15 -08:00
2024-04-16 15:39:48 -07:00
2023-12-29 12:22:28 -08:00
2023-08-21 13:07:20 -07:00
2024-04-16 15:39:48 -07:00
2023-10-18 14:34:17 -07:00
2023-12-12 10:57:08 -08:00
2023-10-25 16:47:14 -07:00
2024-04-25 10:07:27 -07:00
2022-10-03 14:03:05 -07:00
2023-12-12 10:11:32 +01:00
2024-04-16 15:39:48 -07:00
2023-08-18 10:12:36 -07:00
2024-03-21 14:41:00 -07:00
2024-01-22 10:31:08 +01:00
2024-03-04 17:01:26 -08:00
2023-12-12 10:57:07 -08:00
2023-12-29 11:58:56 -08:00
2024-02-22 10:24:54 -08:00
2023-04-12 17:36:23 -07:00
2024-04-16 15:39:48 -07:00
2024-03-31 11:32:26 +09:00
2023-08-24 16:20:30 -07:00
2024-02-24 15:53:40 -08:00
2024-03-04 17:01:25 -08:00
2024-03-04 17:01:21 -08:00
2024-02-22 10:24:40 -08:00
2024-04-16 15:39:50 -07:00
2024-02-22 10:24:55 -08:00
2024-04-05 11:21:31 -07:00
2024-03-06 13:04:18 -08:00
2024-03-13 18:38:13 -04:00
2023-12-29 11:58:26 -08:00
2024-03-13 12:12:21 -07:00
2023-12-29 11:58:56 -08:00
2024-02-23 17:28:43 -08:00
2023-08-21 13:07:20 -07:00
2024-03-04 17:01:22 -08:00
2024-03-06 13:04:17 -08:00
2022-10-03 14:02:43 -07:00
2024-03-22 10:41:13 -07:00
2024-02-22 15:27:17 -08:00
2023-08-18 10:12:41 -07:00
2023-12-12 10:57:02 -08:00
2024-02-21 16:00:03 -08:00
2023-10-18 14:34:18 -07:00
2022-09-26 19:46:25 -07:00
2024-02-23 17:48:19 -08:00
2024-03-04 17:01:16 -08:00
2024-03-14 17:43:30 -07:00
2022-09-11 20:26:01 -07:00
2023-08-18 10:12:31 -07:00
2023-01-18 17:12:52 -08:00
2023-12-29 20:22:11 -08:00
2024-03-04 17:01:27 -08:00
2024-04-16 15:39:51 -07:00
2023-12-10 16:51:50 -08:00
2024-01-08 15:27:15 -08:00
2023-08-24 16:20:18 -07:00
2023-12-20 14:48:12 -08:00
2024-02-23 17:48:38 -08:00
2023-12-10 16:51:53 -08:00
2023-06-19 16:19:29 -07:00
2022-03-08 09:30:46 -05:00
2023-12-14 00:23:17 -08:00
2023-08-18 10:12:25 -07:00
2023-12-10 16:51:39 -08:00
2024-02-22 10:24:47 -08:00
2024-03-04 17:01:19 -08:00
2024-02-22 15:27:20 -08:00
2022-10-03 14:03:05 -07:00
2023-08-21 13:38:02 -07:00
2024-03-26 11:07:23 -07:00
2024-04-16 15:39:51 -07:00
2024-01-08 15:27:15 -08:00
2023-10-04 10:32:26 -07:00
2024-01-05 09:58:32 -08:00
2022-10-03 14:03:07 -07:00
2024-01-08 15:27:15 -08:00
2024-03-14 18:03:09 -07:00
2024-03-12 10:16:56 +01:00
2024-03-12 10:16:56 +01:00
2023-08-18 10:12:53 -07:00
2024-02-21 16:00:01 -08:00
2022-10-03 14:03:36 -07:00
2024-02-22 10:24:54 -08:00
2024-03-04 17:01:26 -08:00
2024-03-12 13:07:16 -07:00
2024-02-20 14:20:48 -08:00
2024-03-14 17:43:30 -07:00
2023-12-10 16:51:42 -08:00
2023-04-12 17:36:23 -07:00
2024-03-26 11:07:23 -07:00
2024-03-14 17:43:30 -07:00
2024-04-05 11:21:30 -07:00
2023-11-28 14:08:38 +01:00
2024-03-14 17:43:30 -07:00
2024-01-08 15:27:15 -08:00
2024-02-21 11:36:50 +05:30
2024-02-23 17:48:31 -08:00
2023-06-19 16:19:27 -07:00
2023-06-19 16:19:27 -07:00
2024-03-04 17:01:28 -08:00
2024-04-24 19:34:26 -07:00