stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Willy Tarreau <w@1wt.eu>
Cc: Sasha Levin <sasha.levin@oracle.com>,
	LKML <linux-kernel@vger.kernel.org>,
	stable <stable@vger.kernel.org>,
	lwn@lwn.net
Subject: Re: [ANNOUNCE] linux-stable security tree
Date: Mon, 11 Apr 2016 23:35:08 -0700	[thread overview]
Message-ID: <20160412063508.GA21417@kroah.com> (raw)
In-Reply-To: <20160412062237.GA507@1wt.eu>

On Tue, Apr 12, 2016 at 08:22:37AM +0200, Willy Tarreau wrote:
> I think we may have more of an issue educating our users than an issue
> with the code we distribute.

I think that's the issue here, combined with users that just don't want
to upgrade as it's "hard" for them.  There's nothing we can do about
making it easier than we already do, and really, taking 200 patches is
just the same work for them to take 100 patches in a release, so I
don't buy the "I only want a small subset of fixes" argument, as it
doesn't make any sense.

So I worry that this tree will give people a _false_ sense of security,
thinking that they have properly covered the needed fixes when really,
there are lots of fixes they didn't even know they needed that got
applied to the "normal" stable tree for issues they will hit.

Also, people need to stop being afraid of the large numbers of stable
patches, and compare it to the overall % of changes, and realize that
what we take in stable releases is really a trivially small number of
the overall changes made to the kernel.  So much so that you might argue
that it's safer to run the real kernel releases and not rely on stable
releases :)

thanks,

greg k-h

  reply	other threads:[~2016-04-12  6:35 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-11 17:53 [ANNOUNCE] linux-stable security tree Sasha Levin
2016-04-11 18:17 ` Jeff Merkey
2016-04-11 19:01   ` Sasha Levin
2016-04-11 18:34 ` Jeff Merkey
2016-04-11 19:02   ` Richard Weinberger
2016-04-11 19:04   ` Sasha Levin
2016-04-11 19:08     ` Jeff Merkey
2016-04-11 18:41 ` Greg KH
2016-04-11 18:58   ` Sasha Levin
2016-04-11 20:09     ` Greg KH
2016-04-11 20:38       ` Sasha Levin
2016-04-11 21:17         ` Willy Tarreau
2016-04-11 22:48           ` Sasha Levin
2016-04-12  6:22             ` Willy Tarreau
2016-04-12  6:35               ` Greg KH [this message]
2016-04-12  8:11                 ` Willy Tarreau
2016-04-12 12:31                   ` Eddie Chapman
2016-04-12 12:52                     ` Willy Tarreau
2016-04-12 13:48                       ` Eddie Chapman

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=20160412063508.GA21417@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lwn@lwn.net \
    --cc=sasha.levin@oracle.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 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).