kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Year 2038 time set problem
Date: Mon, 26 Feb 2018 15:16:32 +0100	[thread overview]
Message-ID: <20180226141632.GA2784@kroah.com> (raw)
In-Reply-To: <CAL9TtUpJFHmP6Q3mdrDQO=jv7GW72eb5LF8pgzZRzfAu3CkswA@mail.gmail.com>

On Mon, Feb 26, 2018 at 02:15:53PM +0100, Piotr Figiel wrote:
> Hi,
> 
> 2018-02-24 16:50 GMT+01:00 Greg KH <greg@kroah.com>:
> > Also note that the 4.1 kernel is very old and obsolete and insecure, and
> > should NOT be used for any devices in the year 2038.
> 
> According to kernel.org website 4.1 has projected EOL in May 2018.

Yes, 3 months from now.

> Is the information about kernel releases on kernel.org irrelevant/
> shouldn't be trusted? Or my understanding of longterm kernel trees is
> incorrect?

No, it is correct, but note that since 4.1.y is about to be end-of-life,
it is receiving very few updates.  No new device should be considering
to use it for their kernel version because it will not be supported very
soon now.

In fact, if you are using 4.1.y, you have already been told to move off
of it as soon as possible for this very reason.

> Which trees do get security updates?

The kernels listed on that page, but be aware that as the end-of-life
time approaches, the releases and updates get very infrequent.  You
should always just update to a newer kernel version, or, if you are
stuck at a specific kernel version due to some hardware or SoC
requirements, get your support from that company as you are already
paying for it.

Hope this helps,

greg k-h

  reply	other threads:[~2018-02-26 14:16 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-23  9:43 Year 2038 time set problem techi eth
2018-02-23 13:18 ` valdis.kletnieks at vt.edu
2018-02-24 13:59   ` techi eth
2018-02-24 15:50     ` Greg KH
2018-02-26 13:15       ` Piotr Figiel
2018-02-26 14:16         ` Greg KH [this message]
2018-02-26 21:19           ` Dave Stevens
2018-02-27  9:22             ` Greg KH
2018-02-26 15:21         ` valdis.kletnieks at vt.edu
2018-02-26 15:36           ` Piotr Figiel
2018-03-01  9:19       ` techi eth
2018-03-01 12:04         ` Greg KH
2018-02-25  5:52     ` valdis.kletnieks at vt.edu
  -- strict thread matches above, loose matches on Subject: below --
2018-03-04  6:59 tali.perry at nuvoton.com
2018-03-04 18:31 ` valdis.kletnieks at vt.edu
2018-03-04 20:20   ` Ruben Safir
2018-03-04 20:54     ` Greg KH
2018-03-04 20:54   ` Greg KH
2018-03-04 22:25     ` valdis.kletnieks at vt.edu
2018-03-05  5:54       ` Greg KH
2018-03-04 20:47 Alex Arvelaez
2018-03-04 22:24 ` valdis.kletnieks at vt.edu
2018-03-05  2:21   ` Ruben Safir
2018-03-05  4:15     ` valdis.kletnieks at vt.edu
2018-03-05  4:50       ` Ruben Safir
2018-03-05  8:50         ` valdis.kletnieks at vt.edu
2018-03-05 12:15           ` Ruben Safir
2018-03-05 12:31           ` Ruben Safir
2018-03-05 12:34           ` Ruben Safir
2018-03-05 12:57             ` Darin Avery
2018-03-05  4:57       ` Ruben Safir
2018-03-05  5:03       ` Ruben Safir
2018-03-05  2:35 Alex Arvelaez
2018-03-05  3:14 ` Ruben Safir
2018-03-05  6:00   ` Greg KH
2018-03-05  6:15     ` Ruben Safir
2018-03-05  6:26       ` Greg KH
2018-03-05 19:52         ` Ruben Safir
2018-03-05 19:54         ` Ruben Safir
2018-03-05 15:43   ` Jeffrey Walton
2018-03-05 11:29 ` Bernd Petrovitsch
2018-03-05 12:20   ` Ruben Safir
2018-03-05 12:43     ` valdis.kletnieks at vt.edu
2018-03-05 12:54     ` Greg KH
2018-03-05  4:07 Alex Arvelaez
2018-03-05  4:16 ` Ruben Safir
2018-03-05  5:53   ` Greg KH
2018-03-05  6:04     ` Ruben Safir
2018-03-05 15:35 Alex Arvelaez
2018-03-05 16:49 ` Greg KH

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=20180226141632.GA2784@kroah.com \
    --to=greg@kroah.com \
    --cc=kernelnewbies@lists.kernelnewbies.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).