linux-kernel - Re: stable cc's in linux -next was Re: [BUG] x86: bootmem broken on SGI UV

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: <AANLkTikKNHp85iHNunSnC6EJkS5P3M5-OEN3yzzFw_Q8@mail.gmail.com>
Date:	Mon, 11 Oct 2010 11:21:20 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Greg KH <greg@...ah.com>
Cc:	Dave Airlie <airlied@...il.com>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Stephen Rothwell <sfr@...b.auug.org.au>
Subject: Re: stable cc's in linux -next was Re: [BUG] x86: bootmem broken on
 SGI UV

On Mon, Oct 11, 2010 at 10:31 AM, Greg KH <greg@...ah.com> wrote:
>
>> So I have no solution to it. I just don't think stable has been quite
>> as stable as people would wish for.
>
> It hasn't?  I haven't heard people saying anything about this before, in
> fact, people seem to get upset at me when I reject the stuff they are
> sending me for inclusion which don't meet the stable criteria.

Quickly searching my email for "bisect" and "stable" gets a few hits
for 2.6.35. One was the problems with the stack guard page in
2.6.35.2, another was some CPU usage issue in 2.6.35.4.  And there was
the scheduler problem in 2.6.32.y or whatever (but that was a "done
differently from mainline" situation, so it was a different kind of
patch entirely).

And there probably are others that my silly search just didn't see.

> Not that I'm trying to say, "it could be worse", just that, "what could
> be done better?"

I really don't know. I suspect that a certain amount of problems are
always going to be inevitable. It's not like you can avoid regressions
entirely, at least not unless you take the "it's dead, Jim" approach
to stable.

                     Linus
--
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/