From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mout.kundenserver.de ([212.227.17.24]:64987 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753369AbcHRL6W (ORCPT ); Thu, 18 Aug 2016 07:58:22 -0400 From: Arnd Bergmann To: gregkh@linuxfoundation.org Subject: Re: Patch "jbd2: make journal y2038 safe" has been added to the 4.7-stable tree Date: Thu, 18 Aug 2016 13:51:04 +0200 Cc: jack@suse.cz, tytso@mit.edu, stable@vger.kernel.org, stable-commits@vger.kernel.org References: <14715114801979@kroah.com> In-Reply-To: <14715114801979@kroah.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201608181351.04907.arnd@arndb.de> Sender: stable-owner@vger.kernel.org List-ID: On Thursday 18 August 2016, gregkh@linuxfoundation.org wrote: > This is a note to let you know that I've just added the patch titled > > jbd2: make journal y2038 safe > > to the 4.7-stable tree which can be found at: > http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary > > The filename of the patch is: > jbd2-make-journal-y2038-safe.patch > and it can be found in the queue-4.7 subdirectory. > > If you, or anyone else, feels it should not be added to the stable tree, > please let know about it. > In general, I think adding this sort of patch to stable kernels is pointless, since we still have several hundred other issues that prevent us from running 32-bit kernels after 2038. We have to work our way through all of them, but until we have a stable kernel that at least has a syscall ABI for 64-bit time_t, I wouldn't bother with backporting any of it. That said, there is nothing wrong with the patch, and you don't need to back it out if that causes extra work, the only downside is extra work for people that go through the stable patches individually to decide whether to apply them to some other tree. Arnd