aboutsummaryrefslogtreecommitdiff
path: root/lib/test_fortify/write_overflow-strncpy-src.c
diff options
context:
space:
mode:
authorArd Biesheuvel <[email protected]>2023-02-17 15:23:38 +0100
committerAlexandre Belloni <[email protected]>2023-02-22 21:07:53 +0100
commit668a2abf91143caa226b3ccd0bd4d79ea85935a6 (patch)
treeb02962f76da3b0c2ad123a8425336083bf8127c7 /lib/test_fortify/write_overflow-strncpy-src.c
parent303eac653a181be59674920725142cfbdd5ba4cd (diff)
rtc: efi: Avoid spamming the log on RTC read failure
There are cases where the EFI runtime services may end up in a funny state, e.g., due to a crash in the variable services, and this affects other EFI runtime services as well. That means that, even though GetTime() should not return an error, there are cases where it might, and there is no point in logging such an occurrence multiple times. This works around an issue where user space -apparently- keeps hitting on /dev/rtc if it fails to read the h/w clock, resulting in a tsunami of log spam and a non-responsive system as a result. Cc: Pierre Gondois <[email protected]> Cc: Alexandru Elisei <[email protected]> Link: https://lore.kernel.org/all/[email protected]/ Signed-off-by: Ard Biesheuvel <[email protected]> Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Alexandre Belloni <[email protected]>
Diffstat (limited to 'lib/test_fortify/write_overflow-strncpy-src.c')
0 files changed, 0 insertions, 0 deletions