From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757380AbdJLWkg (ORCPT ); Thu, 12 Oct 2017 18:40:36 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:33640 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755985AbdJLWke (ORCPT ); Thu, 12 Oct 2017 18:40:34 -0400 Date: Thu, 12 Oct 2017 15:40:32 -0700 From: Andrew Morton To: Arnd Bergmann Cc: Jason Wessel , Thomas Gleixner , y2038@lists.linaro.org, John Stultz , Stephen Boyd , Andy Shevchenko , Deepa Dinamani , Ingo Molnar , linux-kernel@vger.kernel.org, kgdb-bugreport@lists.sourceforge.net Subject: Re: [PATCH] kdb: use __ktime_get_real_seconds instead of __current_kernel_time Message-Id: <20171012154032.24a3007c479154d77c2767b4@linux-foundation.org> In-Reply-To: <20171012140659.2749268-1-arnd@arndb.de> References: <20171012140659.2749268-1-arnd@arndb.de> X-Mailer: Sylpheed 3.4.1 (GTK+ 2.24.23; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 12 Oct 2017 16:06:11 +0200 Arnd Bergmann wrote: > kdb is the only user of the __current_kernel_time() interface, which is > not y2038 safe and should be removed at some point. > > The kdb code also goes to great lengths to print the time in a > human-readable format from 'struct timespec', again using a non-y2038-safe > re-implementation of the generic time_to_tm() code. Is it really necessary for the kdb `summary' command to print the time/date? Which puppies would die if we just removed it all?