Zhaoyang Huang
8c61291fd8
mm: fix incorrect vbq reference in purge_fragmented_block
...
xa_for_each() in _vm_unmap_aliases() loops through all vbs. However,
since commit 062eacf57ad9 ("mm: vmalloc: remove a global vmap_blocks
xarray") the vb from xarray may not be on the corresponding CPU
vmap_block_queue. Consequently, purge_fragmented_block() might use the
wrong vbq->lock to protect the free list, leading to vbq->free breakage.
Incorrect lock protection can exhaust all vmalloc space as follows:
CPU0 CPU1
+--------------------------------------------+
| +--------------------+ +-----+ |
+--> | |---->| |------+
| CPU1:vbq free_list | | vb1 |
+--- | |<----| |<-----+
| +--------------------+ +-----+ |
+--------------------------------------------+
_vm_unmap_aliases() vb_alloc()
new_vmap_block()
xa_for_each(&vbq->vmap_blocks, idx, vb)
--> vb in CPU1:vbq->freelist
purge_fragmented_block(vb)
spin_lock(&vbq->lock) spin_lock(&vbq->lock)
--> use CPU0:vbq->lock --> use CPU1:vbq->lock
list_del_rcu(&vb->free_list) list_add_tail_rcu(&vb->free_list, &vbq->free)
__list_del(vb->prev, vb->next)
next->prev = prev
+--------------------+
| |
| CPU1:vbq free_list |
+---| |<--+
| +--------------------+ |
+----------------------------+
__list_add(new, head->prev, head)
+--------------------------------------------+
| +--------------------+ +-----+ |
+--> | |---->| |------+
| CPU1:vbq free_list | | vb2 |
+--- | |<----| |<-----+
| +--------------------+ +-----+ |
+--------------------------------------------+
prev->next = next
+--------------------------------------------+
|----------------------------+ |
| +--------------------+ | +-----+ |
+--> | |--+ | |------+
| CPU1:vbq free_list | | vb2 |
+--- | |<----| |<-----+
| +--------------------+ +-----+ |
+--------------------------------------------+
Here’s a list breakdown. All vbs, which were to be added to
‘prev’, cannot be used by list_for_each_entry_rcu(vb, &vbq->free,
free_list) in vb_alloc(). Thus, vmalloc space is exhausted.
This issue affects both erofs and f2fs, the stacktrace is as follows:
erofs:
[<ffffffd4ffb93ad4>] __switch_to+0x174
[<ffffffd4ffb942f0>] __schedule+0x624
[<ffffffd4ffb946f4>] schedule+0x7c
[<ffffffd4ffb947cc>] schedule_preempt_disabled+0x24
[<ffffffd4ffb962ec>] __mutex_lock+0x374
[<ffffffd4ffb95998>] __mutex_lock_slowpath+0x14
[<ffffffd4ffb95954>] mutex_lock+0x24
[<ffffffd4fef2900c>] reclaim_and_purge_vmap_areas+0x44
[<ffffffd4fef25908>] alloc_vmap_area+0x2e0
[<ffffffd4fef24ea0>] vm_map_ram+0x1b0
[<ffffffd4ff1b46f4>] z_erofs_lz4_decompress+0x278
[<ffffffd4ff1b8ac4>] z_erofs_decompress_queue+0x650
[<ffffffd4ff1b8328>] z_erofs_runqueue+0x7f4
[<ffffffd4ff1b66a8>] z_erofs_read_folio+0x104
[<ffffffd4feeb6fec>] filemap_read_folio+0x6c
[<ffffffd4feeb68c4>] filemap_fault+0x300
[<ffffffd4fef0ecac>] __do_fault+0xc8
[<ffffffd4fef0c908>] handle_mm_fault+0xb38
[<ffffffd4ffb9f008>] do_page_fault+0x288
[<ffffffd4ffb9ed64>] do_translation_fault[jt]+0x40
[<ffffffd4fec39c78>] do_mem_abort+0x58
[<ffffffd4ffb8c3e4>] el0_ia+0x70
[<ffffffd4ffb8c260>] el0t_64_sync_handler[jt]+0xb0
[<ffffffd4fec11588>] ret_to_user[jt]+0x0
f2fs:
[<ffffffd4ffb93ad4>] __switch_to+0x174
[<ffffffd4ffb942f0>] __schedule+0x624
[<ffffffd4ffb946f4>] schedule+0x7c
[<ffffffd4ffb947cc>] schedule_preempt_disabled+0x24
[<ffffffd4ffb962ec>] __mutex_lock+0x374
[<ffffffd4ffb95998>] __mutex_lock_slowpath+0x14
[<ffffffd4ffb95954>] mutex_lock+0x24
[<ffffffd4fef2900c>] reclaim_and_purge_vmap_areas+0x44
[<ffffffd4fef25908>] alloc_vmap_area+0x2e0
[<ffffffd4fef24ea0>] vm_map_ram+0x1b0
[<ffffffd4ff1a3b60>] f2fs_prepare_decomp_mem+0x144
[<ffffffd4ff1a6c24>] f2fs_alloc_dic+0x264
[<ffffffd4ff175468>] f2fs_read_multi_pages+0x428
[<ffffffd4ff17b46c>] f2fs_mpage_readpages+0x314
[<ffffffd4ff1785c4>] f2fs_readahead+0x50
[<ffffffd4feec3384>] read_pages+0x80
[<ffffffd4feec32c0>] page_cache_ra_unbounded+0x1a0
[<ffffffd4feec39e8>] page_cache_ra_order+0x274
[<ffffffd4feeb6cec>] do_sync_mmap_readahead+0x11c
[<ffffffd4feeb6764>] filemap_fault+0x1a0
[<ffffffd4ff1423bc>] f2fs_filemap_fault+0x28
[<ffffffd4fef0ecac>] __do_fault+0xc8
[<ffffffd4fef0c908>] handle_mm_fault+0xb38
[<ffffffd4ffb9f008>] do_page_fault+0x288
[<ffffffd4ffb9ed64>] do_translation_fault[jt]+0x40
[<ffffffd4fec39c78>] do_mem_abort+0x58
[<ffffffd4ffb8c3e4>] el0_ia+0x70
[<ffffffd4ffb8c260>] el0t_64_sync_handler[jt]+0xb0
[<ffffffd4fec11588>] ret_to_user[jt]+0x0
To fix this, introducee cpu within vmap_block to record which this vb
belongs to.
Link: https://lkml.kernel.org/r/20240614021352.1822225-1-zhaoyang.huang@unisoc.com
Link: https://lkml.kernel.org/r/20240607023116.1720640-1-zhaoyang.huang@unisoc.com
Fixes: fc1e0d980037 ("mm/vmalloc: prevent stale TLBs in fully utilized blocks")
Signed-off-by: Zhaoyang Huang <zhaoyang.huang@unisoc.com>
Suggested-by: Hailong.Liu <hailong.liu@oppo.com>
Reviewed-by: Uladzislau Rezki (Sony) <urezki@gmail.com>
Cc: Baoquan He <bhe@redhat.com>
Cc: Christoph Hellwig <hch@infradead.org>
Cc: Lorenzo Stoakes <lstoakes@gmail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: <stable@vger.kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
2024-06-24 20:52:08 -07:00
..
2024-05-11 15:41:36 -07:00
2024-04-25 20:55:49 -07:00
2024-04-25 20:55:51 -07:00
2024-06-05 19:19:25 -07:00
2024-05-05 17:53:51 -07:00
2023-10-25 16:47:13 -07:00
2024-02-22 10:24:57 -08:00
2024-04-25 20:56:42 -07:00
2024-02-22 10:24:57 -08:00
2024-04-25 20:56:32 -07:00
2024-04-25 20:56:04 -07:00
2024-06-15 10:43:08 -07:00
2024-05-05 17:53:31 -07:00
2023-12-05 11:17:58 +01:00
2023-06-09 16:25:56 -07:00
2024-05-14 00:31:43 -07:00
2023-06-23 16:59:31 -07:00
2023-06-09 16:25:23 -07:00
2024-06-05 19:19:26 -07:00
2024-04-25 20:56:25 -07:00
2023-06-23 16:58:19 -07:00
2024-05-07 10:37:01 -07:00
2023-12-29 12:22:28 -08:00
2024-04-25 20:55:46 -07:00
2024-06-15 10:43:06 -07:00
2024-05-05 17:53:41 -07:00
2024-04-25 20:56:32 -07:00
2023-10-25 16:47:14 -07:00
2024-06-05 19:19:26 -07:00
2024-05-05 17:53:45 -07:00
2023-12-12 10:11:32 +01:00
2024-06-15 10:43:05 -07:00
2023-08-18 10:12:36 -07:00
2024-05-19 09:21:03 -07:00
2024-01-22 10:31:08 +01:00
2024-05-05 17:53:53 -07:00
2024-05-19 14:40:44 -07:00
2024-06-05 19:19:26 -07:00
2024-02-22 10:24:54 -08:00
2024-05-23 19:40:26 -07:00
2024-05-23 19:40:26 -07:00
2023-08-24 16:20:30 -07:00
2024-06-16 10:17:57 +03:00
2024-06-15 10:43:08 -07:00
2024-03-04 17:01:21 -08:00
2024-05-05 17:53:35 -07:00
2024-05-24 11:55:08 -07:00
2024-05-05 17:53:26 -07:00
2024-06-15 10:43:07 -07:00
2024-04-25 20:56:19 -07:00
2024-06-05 19:19:26 -07:00
2024-05-05 17:53:49 -07:00
2024-03-13 12:12:21 -07:00
2024-05-19 09:21:03 -07:00
2024-06-15 10:43:07 -07:00
2023-08-21 13:07:20 -07:00
2024-04-25 20:56:19 -07:00
2024-06-15 10:43:05 -07:00
2024-05-23 19:40:26 -07:00
2024-02-22 15:27:17 -08:00
2024-04-11 13:18:36 -04:00
2023-12-12 10:57:02 -08:00
2024-05-23 19:40:26 -07:00
2024-05-23 19:40:26 -07:00
2024-05-23 19:40:26 -07:00
2024-05-19 09:21:03 -07:00
2024-04-25 20:56:32 -07:00
2024-06-15 10:43:05 -07:00
2024-04-25 20:56:14 -07:00
2024-06-05 19:19:23 -07:00
2024-04-25 20:56:04 -07:00
2024-05-19 14:40:44 -07:00
2023-12-10 16:51:50 -08:00
2024-01-08 15:27:15 -08:00
2024-06-15 10:43:04 -07:00
2024-05-05 17:53:45 -07:00
2024-05-19 09:21:03 -07:00
2023-12-10 16:51:53 -08:00
2024-04-25 20:55:56 -07:00
2024-04-25 20:55:49 -07:00
2024-04-25 20:55:56 -07:00
2024-05-07 10:37:00 -07:00
2023-12-10 16:51:39 -08:00
2024-02-22 10:24:47 -08:00
2024-05-19 09:21:03 -07:00
2024-05-11 15:41:35 -07:00
2023-08-21 13:38:02 -07:00
2024-03-26 11:07:23 -07:00
2024-06-15 10:43:08 -07:00
2024-04-25 20:55:57 -07:00
2023-10-04 10:32:26 -07:00
2024-01-05 09:58:32 -08:00
2024-01-08 15:27:15 -08:00
2024-05-19 09:21:03 -07:00
2024-05-19 09:21:03 -07:00
2024-06-05 19:19:26 -07:00
2023-08-18 10:12:53 -07:00
2024-05-05 17:53:40 -07:00
2024-04-25 20:56:37 -07:00
2024-04-25 20:56:40 -07:00
2024-05-05 17:53:50 -07:00
2024-02-20 14:20:48 -08:00
2024-05-21 08:34:51 -07:00
2024-04-25 20:56:43 -07:00
2024-05-19 09:21:03 -07:00
2024-06-17 12:00:22 -07:00
2024-06-24 20:52:08 -07:00
2023-11-28 14:08:38 +01:00
2024-06-05 19:19:23 -07:00
2024-04-15 14:31:47 +02:00
2024-05-07 10:36:59 -07:00
2024-04-25 20:55:48 -07:00
2024-04-25 20:55:48 -07:00
2024-04-25 20:55:48 -07:00
2024-04-25 20:55:48 -07:00
2024-05-05 17:53:38 -07:00