stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sasha Levin <sasha.levin@oracle.com>
To: Willy Tarreau <w@1wt.eu>
Cc: LKML <linux-kernel@vger.kernel.org>,
	stable <stable@vger.kernel.org>,
	lwn@lwn.net
Subject: Re: stable-security kernel updates
Date: Thu, 21 Apr 2016 10:16:20 -0400	[thread overview]
Message-ID: <5718E0B4.4070208@oracle.com> (raw)
In-Reply-To: <20160421125649.GA9926@1wt.eu>

On 04/21/2016 08:56 AM, Willy Tarreau wrote:
> On Wed, Apr 20, 2016 at 03:50:34PM -0400, Sasha Levin wrote:
>> Hi all,
>>
>> Updates for stable-security kernels have been released:
>>
>> 	- v3.12.58-security
>> 	- v3.14.67-security
>> 	- v3.18.31-security
>> 	- v4.1.22-security
>> 	- v4.4.8-security
>> 	- v4.5.2-security
> 
> Sasha, regardless the rest of the discussion in this thread, I find
> myself confused by the naming above. For me, 3.12.58-something means
> "something" on top of 3.12.58. Many (most? all?) forks work like this,
> but here it seems that instead it's 3.12 + your selection of fixes
> from kernels up to 3.12.58. I guess it would be much less confusing to
> call it something like 3.12.0-security58 or something like this (or
> maybe simply 3.12.0.58). Some people might be tempted to upgrade from
> 3.12.40 to 3.12.58-security and will possibly discover some breakage
> due to bugs that were fixed between 3.12 and 3.12.40 and which are not
> fixed in 3.12.58-security.

That makes sense. I'll change that.


Thanks,
Sasha


      reply	other threads:[~2016-04-21 14:16 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-20 19:50 stable-security kernel updates Sasha Levin
2016-04-21  6:43 ` Jiri Slaby
2016-04-21  7:11   ` Willy Tarreau
2016-04-21 11:27     ` Sasha Levin
2016-04-21 12:36       ` Greg KH
2016-04-21 14:01         ` Sasha Levin
2016-04-21 14:12           ` Willy Tarreau
2016-04-21 11:11   ` Sasha Levin
2016-04-21 11:59     ` Jiri Slaby
2016-04-21 12:05       ` Jiri Slaby
2016-04-21 12:39         ` Greg KH
2016-04-21 12:50           ` Willy Tarreau
2016-04-21 13:54           ` Sasha Levin
2016-04-21 14:13             ` Jiri Slaby
2016-04-21 14:19               ` Willy Tarreau
2016-04-21 14:27               ` Sasha Levin
2016-04-21 14:33                 ` Willy Tarreau
2016-04-25 23:14                   ` Ben Hutchings
2016-04-26  4:40                     ` Willy Tarreau
2016-04-21 13:53       ` Sasha Levin
2016-04-21 14:54         ` Jiri Slaby
2016-04-21 15:50           ` Sasha Levin
2016-04-21 19:32           ` Sasha Levin
2016-04-21 12:26     ` Bjørn Mork
2016-04-21 12:56 ` Willy Tarreau
2016-04-21 14:16   ` Sasha Levin [this message]

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=5718E0B4.4070208@oracle.com \
    --to=sasha.levin@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lwn@lwn.net \
    --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).