public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Knoth <adi@drcomp.erfurt.thur.de>
To: linux-kernel@vger.kernel.org
Subject: Release of 2.4.21
Date: Thu, 20 Mar 2003 20:56:57 +0100	[thread overview]
Message-ID: <20030320195657.GA3270@drcomp.erfurt.thur.de> (raw)

Hi,

how about releasing 2.4.21 with the ptrace()-fix applied immediately
like it has been done with 2.2.25?

I think it's a serious bug and therefore it's time for a security-update.

If you think of ISC bind, PHP, sendmail or other software a new release
follows right after the availability of the patch. I'd like Linux
(and glibc as well) to do the same. You cannot call 2.4.20 a stable kernel
with such a bug, so as a leader of the 2.4.x-series you cannot call the
whole branch "stable".

World needs to update, best way to enforce is by a new release.

-- 
mail: adi@thur.de  	http://adi.thur.de	PGP: v2-key via keyserver

Das letzte Schoene, das in C geschrieben wurde, war Schuberts 9. Sinfonie.

             reply	other threads:[~2003-03-20 19:47 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-20 19:56 Adrian Knoth [this message]
2003-03-20 20:21 ` Release of 2.4.21 Sebastian D.B. Krause
2003-03-20 20:34   ` Jeff Garzik
2003-03-20 20:42     ` Christoph Hellwig
2003-03-20 20:53       ` Jeff Garzik
2003-03-20 21:05         ` David Lang
2003-03-21  1:55       ` Andrew Morton
2003-03-21  0:13         ` John Bradford
2003-03-21  1:30           ` Samuel Flory
2003-03-21  9:33             ` John Bradford
2003-03-21  8:40           ` Bernd Petrovitsch
2003-03-21  9:23             ` John Bradford
2003-03-21 21:53               ` Daniel Egger
2003-03-22  8:27                 ` John Bradford
2003-03-22 14:54                   ` Daniel Egger
2003-03-21  1:01 ` Alan Cox
2003-03-21  0:04   ` David Lang
     [not found] <20030320200019$6ddc@gated-at.bofh.it>
     [not found] ` <20030320203015$4839@gated-at.bofh.it>
2003-03-20 20:43   ` Florian Weimer
2003-03-20 21:03     ` Jeff Garzik
2003-03-20 21:33       ` H. Peter Anvin
2003-03-20 22:08       ` Sebastian D.B. Krause
2003-03-21 11:06         ` Oliver Feiler
2003-03-20 22:18       ` Arador
2003-03-21  1:20       ` Chris Wright
  -- strict thread matches above, loose matches on Subject: below --
2003-03-20 21:17 Dow, Benjamin
2003-03-21  0:57 ` Alan Cox
     [not found] <20030320205011$1378@gated-at.bofh.it>
     [not found] ` <20030320205011$0acb@gated-at.bofh.it>
     [not found]   ` <20030320205011$2c88@gated-at.bofh.it>
     [not found]     ` <20030320211011$5967@gated-at.bofh.it>
2003-03-20 21:48       ` Florian Weimer

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=20030320195657.GA3270@drcomp.erfurt.thur.de \
    --to=adi@drcomp.erfurt.thur.de \
    --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