From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Security updates of Linux kernel
Date: Mon, 26 Feb 2018 18:08:37 +0100 [thread overview]
Message-ID: <20180226170837.GA11737@kroah.com> (raw)
In-Reply-To: <87tvu3bsrd.fsf@miraculix.mork.no>
On Mon, Feb 26, 2018 at 05:49:42PM +0100, Bj?rn Mork wrote:
> Greg KH <greg@kroah.com> writes:
>
> > For a full description on this whole thing, please see this post where I
> > describe how the kernel developers treat "security" bugs, and how to
> > ensure you are running a secure system:
> > http://www.kroah.com/log/blog/2018/02/05/linux-kernel-release-model/
>
> "At the current kernel release rate, the number will change to 5.x
> sometime in 2018."
>
> That's bold. Could cost you some very exclusive whisky if I understand
> the version numbering process correctly.
I would be glad to pay that price :)
next prev parent reply other threads:[~2018-02-26 17:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-26 15:24 Security updates of Linux kernel (was: Re: Year 2038 time set problem) Piotr Figiel
2018-02-26 16:04 ` Greg KH
2018-02-26 16:49 ` Security updates of Linux kernel Bjørn Mork
2018-02-26 17:08 ` Greg KH [this message]
2018-02-26 17:31 ` Konstantin Ryabitsev
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=20180226170837.GA11737@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).