kernel/crash_core.c: print timestamp using time64_t
The get_seconds() call returns a 32-bit timestamp on some architectures, and will overflow in the future. The newer ktime_get_real_seconds() always returns a 64-bit timestamp that does not suffer from this problem. Link: http://lkml.kernel.org/r/20180618150329.941903-1-arnd@arndb.de Signed-off-by: Arnd Bergmann <arnd@arndb.de> Reviewed-by: Andrew Morton <akpm@linux-foundation.org> Cc: Dave Young <dyoung@redhat.com> Cc: Baoquan He <bhe@redhat.com> Cc: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com> Cc: Petr Tesarik <ptesarik@suse.cz> Cc: Marc-Andr Lureau <marcandre.lureau@redhat.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
This commit is contained in:
parent
203583990c
commit
91bc9aaf74
1 changed files with 1 additions and 1 deletions
|
@ -344,7 +344,7 @@ void crash_save_vmcoreinfo(void)
|
|||
if (vmcoreinfo_data_safecopy)
|
||||
vmcoreinfo_data = vmcoreinfo_data_safecopy;
|
||||
|
||||
vmcoreinfo_append_str("CRASHTIME=%ld\n", get_seconds());
|
||||
vmcoreinfo_append_str("CRASHTIME=%lld\n", ktime_get_real_seconds());
|
||||
update_vmcoreinfo_note();
|
||||
}
|
||||
|
||||
|
|
Loading…
Reference in a new issue