mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Frank Steiner <fsteiner-mail@bio.ifi.lmu.de>
Cc: Gregory Boyce <gboyce@badbelly.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Kernel releases for security updates
Date: Sat, 15 Jan 2005 00:32:43 +0000	[thread overview]
Message-ID: <1105743308.9839.21.camel@localhost.localdomain> (raw)
In-Reply-To: <41E77C76.3070204@bio.ifi.lmu.de>

On Gwe, 2005-01-14 at 08:01, Frank Steiner wrote:
> I guess the new -as tree is more or less achieving what you want. If
> Andres gets enough support from other people, it might be possible to
> maintain even more than one or two former releases...

The problem is deciding what goes into such a tree. Do you go security
fixes only which nobody afaik is doing now, do you mix them with key
fixes and if so how far do you add fixes - thats a real PITA because you
can get odd clear fixes for minor problems (eg NFS df) that have never
been tested hard standalone. You can also get dependancies on
non-security fixes for security - -ac for example included my IDE work
to deal with the various IDE exploits/races. Though only minor security
wise there isn't a trivial fix for these with the broken locking in
Linus IDE and its going to take time for Bartlomiej to be happy with my
locking changes.


Alan


      reply	other threads:[~2005-01-15  1:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-12 19:45 Gregory Boyce
2005-01-13 15:36 ` Alan Cox
2005-01-14  8:01 ` Frank Steiner
2005-01-15  0:32   ` Alan Cox [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=1105743308.9839.21.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=fsteiner-mail@bio.ifi.lmu.de \
    --cc=gboyce@badbelly.com \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®