mirror of
https://github.com/zephyrproject-rtos/zephyr
synced 2025-09-15 21:52:34 +00:00
ace11bbefd
If maxsize is smaller than _MPOOL_MINBLK, then Z_MPOOL_LVLS() will be 0. That means the loop in z_sys_mem_pool_base_init() that initializes the block free list for the nonexistent level 0 will corrupt whatever memory at the location the zero-sized struct sys_mem_pool_lvl array was located. And the corruption happens to be done with a perfectly legit memory pool block address which makes for really nasty bugs to solve. This is more likely on 64-bit systems due to _MPOOL_MINBLK being twice the size of 32-bit systems. Let's prevent that with a build-time assertion on maxsize when defining a memory pool, and adjust the affected test accordingly. Signed-off-by: Nicolas Pitre <npitre@baylibre.com> |
||
|---|---|---|
| .. | ||
| arm_irq_vector_table | ||
| arm_ramfunc | ||
| arm_runtime_nmi | ||
| arm_zero_latency_irqs | ||
| boot_page_table | ||
| common | ||
| context | ||
| critical | ||
| device | ||
| early_sleep | ||
| fatal | ||
| fifo | ||
| fp_sharing | ||
| gen_isr_table | ||
| interrupt | ||
| lifo | ||
| mbox | ||
| mem_heap/mheap_api_concept | ||
| mem_pool | ||
| mem_protect | ||
| mem_slab | ||
| mp | ||
| msgq/msgq_api | ||
| mutex | ||
| obj_tracing | ||
| pending | ||
| pipe | ||
| poll | ||
| profiling/profiling_api | ||
| queue | ||
| sched | ||
| semaphore | ||
| sleep | ||
| smp | ||
| spinlock | ||
| stack | ||
| static_idt | ||
| threads | ||
| tickless | ||
| timer | ||
| workq | ||
| xip | ||