Date: Thu, 21 Apr 2016 21:36:31 +0900
From: Greg KH <greg@kroah.com>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: Willy Tarreau <w@1wt.eu>, Jiri Slaby <jslaby@suse.cz>,
        LKML <linux-kernel@vger.kernel.org>, stable <stable@vger.kernel.org>,
        lwn@lwn.net
Subject: Re: stable-security kernel updates
Message-ID: <20160421123631.GA19248@kroah.com>
References: <5717DD8A.4000707@oracle.com>
 <571876AB.2060106@suse.cz>
 <20160421071157.GC9359@1wt.eu>
 <5718B92B.3080105@oracle.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5718B92B.3080105@oracle.com>
User-Agent: Mutt/1.6.0 (2016-04-01)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 957
Lines: 28

On Thu, Apr 21, 2016 at 07:27:39AM -0400, Sasha Levin wrote:
> Hey Willy,
> 
> On 04/21/2016 03:11 AM, Willy Tarreau wrote:
> > This illustrates exactly what I suspected would happen because that's the
> > same trouble we all face when picking backports for our respective trees
> > except that since the selection barrier is much higher here, lots of
> > important ones will be missing
> 
> Right. I fully agree that there will be important security commits that'll
> get missed, whether because they were missed in the stable selection or
> the stable-security selection.
> 
> I'd like to point out again that updating the entire stable tree is the
> preferable way to patch against security (and non-security) issues.

s/preferable/only/ :)

> The
> stable-security tree is a best-effort solution to provide a stop-gap in
> between said stable tree updates.

What are you "stop-gapping" then?  The 7-10 days between stable
releases?

confused,

greg k-h