diff options
author | Stephen Brennan <stephen.s.brennan@oracle.com> | 2022-10-27 13:50:08 -0700 |
---|---|---|
committer | Andrew Morton <akpm@linux-foundation.org> | 2022-11-30 16:13:17 -0800 |
commit | 08fc35f31b9e14cb4e8ba5bf43f824559dbdbe88 (patch) | |
tree | f88f15b0dc8588bfc3b66105021512413f933041 /fs/erofs | |
parent | 3965292ad0ca70320f1c632f2ac3b886c88b9e80 (diff) | |
download | linux-08fc35f31b9e14cb4e8ba5bf43f824559dbdbe88.tar.gz linux-08fc35f31b9e14cb4e8ba5bf43f824559dbdbe88.tar.bz2 linux-08fc35f31b9e14cb4e8ba5bf43f824559dbdbe88.zip |
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/20221027205008.312534-1-stephen.s.brennan@oracle.com
Signed-off-by: Stephen Brennan <stephen.s.brennan@oracle.com>
Acked-by: Baoquan He <bhe@redhat.com>
Cc: Dave Young <dyoung@redhat.com>
Cc: Vivek Goyal <vgoyal@redhat.com>
Cc: Kees Cook <keescook@chromium.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Diffstat (limited to 'fs/erofs')
0 files changed, 0 insertions, 0 deletions