[<prev] [next>] [day] [month] [year] [list]
Message-Id: <20180618150329.941903-1-arnd@arndb.de>
Date: Mon, 18 Jun 2018 17:03:01 +0200
From: Arnd Bergmann <arnd@...db.de>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Arnd Bergmann <arnd@...db.de>, Dave Young <dyoung@...hat.com>,
Xunlei Pang <xlpang@...hat.com>, Baoquan He <bhe@...hat.com>,
"Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>,
Petr Tesarik <ptesarik@...e.cz>,
Matthew Wilcox <mawilcox@...rosoft.com>,
Marc-André Lureau <marcandre.lureau@...hat.com>,
linux-kernel@...r.kernel.org
Subject: [PATCH] crash: 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.
Signed-off-by: Arnd Bergmann <arnd@...db.de>
---
kernel/crash_core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/crash_core.c b/kernel/crash_core.c
index b66aced5e8c2..9612b2571bd6 100644
--- a/kernel/crash_core.c
+++ b/kernel/crash_core.c
@@ -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();
}
--
2.9.0
Powered by blists - more mailing lists