linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: jw schultz <jw@pegasys.ws>
To: "Richard B. Tilley  (Brad)" <rtilley@vt.edu>
Cc: Adrian Bunk <bunk@fs.tum.de>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Bugs and Releases Numbers
Date: Mon, 13 Jan 2003 14:52:17 -0800	[thread overview]
Message-ID: <20030113225217.GC17075@pegasys.ws> (raw)
In-Reply-To: <1042471046.28000.42.camel@oubop4.bursar.vt.edu>

On Mon, Jan 13, 2003 at 10:17:22AM -0500, Richard B. Tilley  (Brad) wrote:
> So, if a major security bug was discovered in stable that impacted many
> systems in a very fundamental way, then a patch would be written and
> applied right away and a new kernel would be released, no?

No.  A new kernel need not be released right away.  Patches
would be made available for affected recent releases.
Anyone running self-built downloaded kernels is expected to
be able to patch them when needed.  Distributions would
apply the patch to their trees and make the new kernel
(source and binaries) available through their usual security
update channels.

It simply isn't necessary to rush a release (contrary to the
principles of stable) just because there is a security hole.
Patches are sufficient.  Besides, most sites run the
distribution kernels anyway so they will get the fix through
those channels.


> If that ever happened, what would become of the patches that had been in
> pre? Would they be included in the new kernel too, or not?
> 
> On Mon, 2003-01-13 at 10:07, Adrian Bunk wrote:
> > On Mon, Jan 13, 2003 at 09:53:36AM -0500, Richard B. Tilley  (Brad) wrote:
> > 
> > > Hello,
> > 
> > Hi Richard,
> > 
> > > How are bug patches worked into the current stable release? For example,
> > > the ext3 file corruption bug in 2.4.20, was that patch worked into the
> > > kernel or will it be included in 2.4.21? I'm confused about the exact
> > > details of this type of thing. If the patch was worked in to 2.4.20, how
> > > can one tell as the release number doesn't/hasn't changed?
> > >...
> > 
> > the kernel that was released as 2.4.20 will never be changed.
> > 
> > The ext3 problems are fixed in the 2.4.21-pre kernels and the fixed ext3 
> > code will be in 2.4.21.
> > 
> > > Thank you,
> > > 
> > > Brad
> > 
> > cu
> > Adrian
> > 
> > -- 
> > 
> >        "Is there not promise of rain?" Ling Tan asked suddenly out
> >         of the darkness. There had been need of rain for many days.
> >        "Only a promise," Lao Er said.
> >                                        Pearl S. Buck - Dragon Seed
> > 
> -- 
> Richard B. Tilley (Brad), System Administrator & Web Developer
> Virginia Tech, Office of the University Bursar
> Phone: 540.231.6277
> Fax: 540.231.3238
> Page: 557.0891
> Web: http://www.bursar.vt.edu
> GPG Key: http://www.bursar.vt.edu/rtilley/pgpkey



-- 
________________________________________________________________
	J.W. Schultz            Pegasystems Technologies
	email address:		jw@pegasys.ws

		Remember Cernan and Schmitt

  reply	other threads:[~2003-01-13 22:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-13 14:53 Bugs and Releases Numbers Richard B. Tilley  (Brad)
2003-01-13 15:07 ` Adrian Bunk
2003-01-13 15:17   ` Richard B. Tilley  (Brad)
2003-01-13 22:52     ` jw schultz [this message]
2003-01-14 16:37       ` Richard B. Tilley  (Brad)

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=20030113225217.GC17075@pegasys.ws \
    --to=jw@pegasys.ws \
    --cc=bunk@fs.tum.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rtilley@vt.edu \
    /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).