This series tries to fix the potential cmem->ranges out of bounds.
On the v1 version, there are still some issues that need to be
discussed, as follows:
1) Whether we need have the cmem->ranges[] partly changed, or keep it
unchanged when OOB happened. Previously discussed link:[1].
2) Set cmem->max_nr_ranges in crash_setup_memmap_entries() to 1 or 2.
Previously discussed link:[2].
3) To enhance crash_setup_memmap_entries() readability, how to move
code. Previously discussed link:[2].
v2:
- Fix potential out of bounds in crash_setup_memmap_entries().
- Add a comment in fill_up_crash_elf_data() to explain why the array
size do not need to be changed.
v1:
Link: https://lore.kernel.org/all/20231127025641.62210-1-fuqiang.wang@xxxxxxxxxxxx/
[1]: https://lore.kernel.org/all/ZXrY7QbXAlxydsSC@MiWiFi-R3L-srv/
[2]: https://lore.kernel.org/all/273284e8-7680-4f5f-8065-c5d780987e59@xxxxxxxxxxxx/
fuqiang wang (2):
x86/kexec: Fix potential out of bounds in crash_setup_memmap_entries()
kexec: Fix potential out of bounds in crash_exclude_mem_range()
arch/x86/kernel/crash.c | 20 ++++++++++++++------
kernel/crash_core.c | 7 +++----
2 files changed, 17 insertions(+), 10 deletions(-)
--
2.42.0
_______________________________________________
kexec mailing list
kexec@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/kexec
