From: Mason <slash.tmp@free.fr>
To: Willy Tarreau <w@1wt.eu>
Cc: Greg KH <greg@kroah.com>, stable@vger.kernel.org
Subject: Re: Next LTS release
Date: Wed, 8 Jun 2016 23:39:34 +0200 [thread overview]
Message-ID: <57589096.2040600@free.fr> (raw)
In-Reply-To: <20160608181411.GB20944@1wt.eu>
On 08/06/2016 20:14, Willy Tarreau wrote:
> On Wed, Jun 08, 2016 at 08:22:38AM -0700, Greg KH wrote:
>
>> You can tell them that they are running insecure kernels that are
>> trivial to break into, and provide them with the latest kernel release
>> to resolve that.
>
> FWIW I just checked, and since we dropped 2.6.32.y 3 months ago, at least
> 2-3 null pointer dereferences affect it, that can be used either just to
> crash the system, or even to gain privileges under certain conditions.
Would you believe me if I told you that we provide kernel version
3.4.39 because "applying security fixes breaks compatibility with
binary kernel modules" ?
What's worse, some customers agree with that "logic".
Regards.
next prev parent reply other threads:[~2016-06-08 21:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-06 7:36 Next LTS release Mason
2016-06-08 1:56 ` Greg KH
2016-06-08 12:59 ` Mason
2016-06-08 15:22 ` Greg KH
2016-06-08 18:14 ` Willy Tarreau
2016-06-08 21:39 ` Mason [this message]
2016-06-08 22:04 ` Willy Tarreau
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=57589096.2040600@free.fr \
--to=slash.tmp@free.fr \
--cc=greg@kroah.com \
--cc=stable@vger.kernel.org \
--cc=w@1wt.eu \
/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.