diff options
| author | Stephen Brennan <[email protected]> | 2022-10-27 13:50:08 -0700 |
|---|---|---|
| committer | Andrew Morton <[email protected]> | 2022-11-30 16:13:17 -0800 |
| commit | 08fc35f31b9e14cb4e8ba5bf43f824559dbdbe88 (patch) | |
| tree | f88f15b0dc8588bfc3b66105021512413f933041 /tools/perf/scripts/python/stackcollapse.py | |
| parent | 3965292ad0ca70320f1c632f2ac3b886c88b9e80 (diff) | |
vmcoreinfo: warn if we exceed vmcoreinfo data size
Though vmcoreinfo is intended to be small, at just one page, useful
information is still added to it, so we risk running out of space.
Currently there is no runtime check to see whether the vmcoreinfo buffer
has been exhausted. Add a warning for this case.
Currently, my static checking tool[1] indicates that a good upper bound
for vmcoreinfo size is currently 3415 bytes, but the best time to add
warnings is before the risk becomes too high.
[1] https://github.com/brenns10/kernel_stuff/blob/master/vmcoreinfosize/vmcoreinfosize.py
Link: https://lkml.kernel.org/r/[email protected]
Signed-off-by: Stephen Brennan <[email protected]>
Acked-by: Baoquan He <[email protected]>
Cc: Dave Young <[email protected]>
Cc: Vivek Goyal <[email protected]>
Cc: Kees Cook <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions