From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Year 2038 time set problem
Date: Sun, 4 Mar 2018 21:54:27 +0100 [thread overview]
Message-ID: <20180304205427.GB15059@kroah.com> (raw)
In-Reply-To: <c3dd70c7-542a-c555-9345-d88a59513804@mrbrklyn.com>
On Sun, Mar 04, 2018 at 03:20:48PM -0500, Ruben Safir wrote:
> On 03/04/2018 01:31 PM, valdis.kletnieks at vt.edu wrote:
> > Note that saying "The CPU isn't vulnerable to Meltdown/Spectre, therefor
> > the 4.1 kernel is OK" is *incredibly* wrong.
> >
> > For the record, since 4.1 came out, there's been at *least* a dozen security
> > issues in the Linux kernel that have been a *lot* scarier for security
> > professionals than the Meltdown/Spectre issue. That only got any news coverage
> > because it was an actual hardware design flaw that was believed to be difficult
> > to easily fix with software changes...
>
> By this standard, it is necessary to update the kernel and reboot nearly
> every week. Is that right?
That is correct.
greg k-h
next prev parent reply other threads:[~2018-03-04 20:54 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-04 6:59 Year 2038 time set problem 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 [this message]
2018-03-04 20:54 ` Greg KH
2018-03-04 22:25 ` valdis.kletnieks at vt.edu
2018-03-05 5:54 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2018-03-05 15:35 Alex Arvelaez
2018-03-05 16:49 ` 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 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-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-02-23 9:43 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
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
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=20180304205427.GB15059@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).