aboutsummaryrefslogtreecommitdiff
path: root/lib/test_fortify/write_overflow-strncpy-src.c
diff options
context:
space:
mode:
authorZhiquan Li <[email protected]>2023-10-26 08:39:03 +0800
committerBorislav Petkov (AMD) <[email protected]>2023-11-13 09:53:15 +0100
commit9f3b130048bfa2e44a8cfb1b616f826d9d5d8188 (patch)
treea03ae057b55601a51bde0b54bd640cbe4a1d2f4b /lib/test_fortify/write_overflow-strncpy-src.c
parentb85ea95d086471afb4ad062012a4d73cd328fa86 (diff)
x86/mce: Mark fatal MCE's page as poison to avoid panic in the kdump kernel
Memory errors don't happen very often, especially fatal ones. However, in large-scale scenarios such as data centers, that probability increases with the amount of machines present. When a fatal machine check happens, mce_panic() is called based on the severity grading of that error. The page containing the error is not marked as poison. However, when kexec is enabled, tools like makedumpfile understand when pages are marked as poison and do not touch them so as not to cause a fatal machine check exception again while dumping the previous kernel's memory. Therefore, mark the page containing the error as poisoned so that the kexec'ed kernel can avoid accessing the page. [ bp: Rewrite commit message and comment. ] Co-developed-by: Youquan Song <[email protected]> Signed-off-by: Youquan Song <[email protected]> Signed-off-by: Zhiquan Li <[email protected]> Signed-off-by: Borislav Petkov (AMD) <[email protected]> Reviewed-by: Naoya Horiguchi <[email protected]> Link: https://lore.kernel.org/r/[email protected]
Diffstat (limited to 'lib/test_fortify/write_overflow-strncpy-src.c')
0 files changed, 0 insertions, 0 deletions