linux-kernel - Re: 2.6.18-stable release plans?

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: <20070125010020.GB26654@deepthought>
Date:	Thu, 25 Jan 2007 01:00:20 +0000
From:	Ken Moffat <zarniwhoop@...world.com>
To:	Chris Rankin <rankincj@...oo.com>
Cc:	Mark Rustad <mrustad@...il.com>, Alan <alan@...rguk.ukuu.org.uk>,
	linux-kernel@...r.kernel.org
Subject: Re: 2.6.18-stable release plans?

On Wed, Jan 24, 2007 at 11:45:57PM +0000, Chris Rankin wrote:
> 
> There is a world of difference between a polite request for more information (although I gave you
> everything I had), and fobbing someone off with a story about cosmic rays.
> 
 Chris,

 I doubt there was a single version of the kernel which ever worked
well for all its users.  In a production environment, reverting to an
older version may be the best short-term answer, but if nobody
recognises the problem you won't get any closer to a proper fix.  At
the moment, you have a problem that nobody recognises.  If you're not
willing to test if the problem happens repeatably, (you appear to
have had one failure and immediately reverted to an old kernel), who
do you think will be able to fix it?  And if it turns out it doesn't
fail repeatably, maybe the responses you've received could be
correct.

 The stable team are only there to maintain the current release of
the kernel.  There is no maintenance of earlier releases (except
Adrian's work on 2.6.16), other than what a distro chooses to do to
backport fixes.  Of course, if the problem _is_ reproducible on your
machine and config, you might get asked to try to identify when it
got introduced (e.g. was 2.6.19 itself, or an arbitrary 2.6.19-rc,
ok?).

Ken
-- 
das eine Mal als Tragödie, das andere Mal als Farce
-
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/