public inbox for gentoo-kernel@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Anthony G. Basile" <blueness@gentoo.org>
To: gentoo-kernel@lists.gentoo.org
Subject: Re: [gentoo-kernel] vanilla-kernel sources should not be marked stable for obsolete versions
Date: Fri, 21 Jun 2013 11:46:32 -0400	[thread overview]
Message-ID: <51C47558.1040004@gentoo.org> (raw)
In-Reply-To: <20130621153056.GA2192@woodpecker.gentoo.org>

On 06/21/2013 11:30 AM, Mike Pagano wrote:
> This should be written down and if it's not that's probably on me as I
> am the only kernel person (i think) that was involved in the decision
> and is still around.

Nope, I was there.  It was the IA32 on amd64 syscall local root exploit 
that got us "blogged" about ... remember that :)

Anyhow, no brainer here.  The kernel is not like the other software we 
stabilize.  Somewhere in its configuration space and in the hardware 
space in which it will be run, there are bugs.  Minor version bumps to 
address security issues followed by auto stabilization are the correct 
thing to do.

-- 
Anthony G. Basile, Ph.D.
Gentoo Linux Developer [Hardened]
E-Mail    : blueness@gentoo.org
GnuPG FP  : 1FED FAD9 D82C 52A5 3BAB  DC79 9384 FA6E F52D 4BBA
GnuPG ID  : F52D4BBA


  reply	other threads:[~2013-06-21 15:45 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-21 14:58 [gentoo-kernel] vanilla-kernel sources should not be marked stable for obsolete versions Greg KH
2013-06-21 15:30 ` Mike Pagano
2013-06-21 15:46   ` Anthony G. Basile [this message]
2013-06-21 16:49     ` Greg KH
2013-06-21 16:48   ` Greg KH
2013-06-21 17:20     ` Eric F. GARIOUD
2013-06-21 17:50       ` Greg KH
2013-06-21 19:51         ` Eric F. GARIOUD
2013-06-21 21:03           ` Greg KH
2013-06-21 19:36     ` Mike Pagano
2013-06-21 21:06       ` Greg KH
2013-06-22  0:23   ` Tom Wijsman
2013-06-22  0:02 ` Tom Wijsman
2013-06-22  0:12   ` Greg KH
2013-06-22  0:13   ` Greg KH
2013-06-22  0:45     ` Tom Wijsman
2013-06-22  1:54       ` Anthony G. Basile
2013-06-22  3:47         ` Greg KH
2013-06-22  8:56           ` Anthony G. Basile
2013-06-22 14:43             ` Greg KH
2013-06-22 16:46               ` Anthony G. Basile
2013-06-24 22:05                 ` Greg KH
2013-06-22  3:42       ` Greg KH
2013-06-22  6:45         ` Tom Wijsman
2013-06-24 16:27           ` Greg KH
2013-06-24 23:26             ` Anthony G. Basile
2013-06-24 23:37             ` Tom Wijsman
2013-06-25  7:43               ` Marc Schiffbauer
2013-06-25  3:09             ` Dale
2013-06-25  6:18               ` Douglas Dunn
2013-06-27  4:15                 ` Greg KH
2013-06-27 19:45             ` Mike Pagano
2013-06-27 20:03               ` Anthony G. Basile
2013-06-27 20:21                 ` Mike Pagano
2013-07-06 19:56               ` Greg KH

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=51C47558.1040004@gentoo.org \
    --to=blueness@gentoo.org \
    --cc=gentoo-kernel@lists.gentoo.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