From: Arnd Bergmann <arnd@arndb.de>
To: gregkh@linuxfoundation.org
Cc: jack@suse.cz, tytso@mit.edu, stable@vger.kernel.org,
stable-commits@vger.kernel.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 [thread overview]
Message-ID: <201608181351.04907.arnd@arndb.de> (raw)
In-Reply-To: <14715114801979@kroah.com>
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 <stable@vger.kernel.org> 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
prev parent reply other threads:[~2016-08-18 11:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-18 9:11 Patch "jbd2: make journal y2038 safe" has been added to the 4.7-stable tree gregkh
2016-08-18 11:51 ` Arnd Bergmann [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201608181351.04907.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=jack@suse.cz \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.