linux-kernel - Re: A proposal; making 2.6.20 a bugfix only version.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20061110133101.4e6cddd3@freekitty>
Date:	Fri, 10 Nov 2006 13:31:01 -0800
From:	Stephen Hemminger <shemminger@...l.org>
To:	Al Boldi <a1426z@...ab.com>
Cc:	Arjan van de Ven <arjan@...radead.org>,
	Randy Dunlap <rdunlap@...otime.net>,
	Jesper Juhl <jesper.juhl@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: A proposal; making 2.6.20 a bugfix only version.

On Sat, 11 Nov 2006 00:22:52 +0300
Al Boldi <a1426z@...ab.com> wrote:

> Arjan van de Ven wrote:
> > > The problem is not just simple bugs that surface, it's deeper than that.
> > > Deep structural problems is what plagues 2.6.
> > >
> > > Only a focused model may deal with such problems.
> >
> > can you at least provide a list of such structural problems?
> > In fact, why don't you collect them and mail them out (bi)weekly... that
> > may already do wonders.
> > Look at what Adrian is doing with the regressions; although the response
> > isn't 100% people DO pay attention to it.... so maybe if you post a
> > "structural problems list" people will actually start working on
> > things.. (and of course you can help too ;)
> 
> Ok, things like OOM, scheduling, and block-io.

If you want stability don't change these.  But if you think you
have better heuristics propose them for discussion.

> 
> net looks ok, although I would suggest a redesign for 3.0.

Facts, no vague pronouncements please.


-- 
Stephen Hemminger <shemminger@...l.org>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/