linux-kernel - Re: stable? quality assurance?

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: <201007131230.23039.Martin@lichtvoll.de>
Date:	Tue, 13 Jul 2010 12:30:06 +0200
From:	Martin Steigerwald <Martin@...htvoll.de>
To:	Stefan Richter <stefanr@...6.in-berlin.de>
Cc:	Willy Tarreau <w@....eu>, linux-kernel@...r.kernel.org
Subject: Re: stable? quality assurance?

Am Dienstag 13 Juli 2010 schrieb Stefan Richter:
> ...
> 
> > Is the Linux kernel development really in balance with feature work
> > and  stabilization work? Currently at least from my personal
> > perception it is not. Development goes that fast - can you all cope
> > with that speed? Maybe its just time to slow it down a bit?
> 
> If those who added the regressions are found out and asked to debug and
> fix them, the balance should be corrected and perhaps more precautions
> being taken in the future.  Alas, finding the point in history at which
> the kernel regressed might take a lot more time than to actually fix it
> then.  In that case, maybe give the author of the bug an estimate of
> the volunteered hours that were spent on reporting this bug, to put
> the repercussions into it into perspective.  OTOH I suspect a lack of
> responsibility at the developers is not so much an issue here, more so
> that the number of people who take the time for -rc tests (not to
> mention linux-next tests) and to file reports is rather low.  Plus, a
> good bug report often requires experience or good intuition, besides
> patience and rigor.
> 
> There were discussions in the past on how more enthusiasts who are
> willing and able to test prereleases could be attracted.  But maybe
> (just maybe) there are more ways in which the developers themselves
> could perform more extensive/ more systematic tests.

Well I reported it now, although it contains not nearly as much 
information on how to reproduce it or any other debug information either. 
I just did not report it before cause I didn't find the information I can 
provide very helpful and until yesterday I thought it might just have been 
these two freezes and thats it. But maybe report it early is better than 
not to report it at all.

Bug 16376 -  random - possibly Radeon DRM KMS related - freezes
https://bugzilla.kernel.org/show_bug.cgi?id=16376

I will look in the logs whether I might have luck and find anything this 
afternoon when my students learn vi/vim, but I doubt it.

Ciao,
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7

Download attachment "signature.asc " of type "application/pgp-signature" (199 bytes)