From: Sasha Levin <sasha.levin@oracle.com>
To: Jeff Merkey <linux.mdb@gmail.com>
Cc: 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 15:01:57 -0400 [thread overview]
Message-ID: <570BF4A5.2010808@oracle.com> (raw)
In-Reply-To: <CAO6TR8VgX2DTRJ1eb+iw--_e=pnRRpbs=Vc51=Ge6KM_fbiu+Q@mail.gmail.com>
On 04/11/2016 02:17 PM, Jeff Merkey wrote:
> On 4/11/16, Sasha Levin <sasha.levin@oracle.com> wrote:
>> Hi all,
>>
>>
>> I'd like to announce the linux-stable security tree project. The purpose
>> is to create a derivative tree from the regular stable tree that would
>> contain only commits that fix security vulnerabilities.
>>
>> Quite a few users of the stable trees pointed out that on complex
>> deployments,
>> where validation is non-trivial, there is little incentive to follow the
>> stable tree after the product has been deployed to production. There is no
>> interest in "random" kernel fixes and the only requirements are to keep up
>> with security vulnerabilities.
>>
>> Given this, a few projects preferred to delay important kernel updates, and
>> a few even stopped updating the tree altogether, exposing them to critical
>> vulnerabilities.
>>
>> This project provides an easy way to receive only important security
>> commits,
>> which are usually only a few in each release, and makes it easy to
>> incorporate
>> them into existing projects.
>>
>> The tree is available at:
>>
>> https://git.kernel.org/cgit/linux/kernel/git/sashal/linux-stable-security.git/
>>
>> Support is provided for all active -stable trees
>> (https://www.kernel.org/category/releases.html).
>> Branches/tags for unsupported versions of >=3.0 kernels were also generated
>> for reference.
>>
>>
>> Thanks,
>> Sasha
>>
>>
>>
>
> Hi Sasha,
>
> Can you push a copy of this tree to github like Linus has done with
> torvalds/linux so folks who want to develop on it can fork it from
> there.
Sure! Now pushed to https://github.com/sashalevin/linux-stable-security
Thanks,
Sasha
next prev parent reply other threads:[~2016-04-11 19:02 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 [this message]
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
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=570BF4A5.2010808@oracle.com \
--to=sasha.levin@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux.mdb@gmail.com \
--cc=lwn@lwn.net \
--cc=stable@vger.kernel.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).