linux-kernel - Re: automated test? (was Re: Linux 2.6.17.7)

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]

Date:	Wed, 26 Jul 2006 16:29:32 +0200
From:	Adrian Bunk <bunk@...sta.de>
To:	Andrew de Quincey <adq_dvb@...skialf.net>
Cc:	David Lang <dlang@...italinsight.com>,
	Arnaud Patard <apatard@...driva.com>, Greg KH <gregkh@...e.de>,
	linux-kernel@...r.kernel.org, stable@...nel.org
Subject: Re: automated test? (was Re: Linux 2.6.17.7)

On Wed, Jul 26, 2006 at 03:10:02PM +0100, Andrew de Quincey wrote:
> On Wednesday 26 July 2006 14:02, Adrian Bunk wrote:
>...
> > What bothers me more is that noone tested this patch against the kernel
> > it was applied against.
> >
> > The submitter didn't test it works (he didn't even test the compilation).
> 
> Yes I did - I didn't test the final generated patch unfortunately since I 
> assumed it worked. The kernel I _meant_ to diff against worked perfectly :(

Sorry if this was wrong, it wasn't meant against you personally.

Things do go wrong. That's life.
And you aren't the first person who sent a patch that broke the 
compilation of the next -stable kernel.

The real problem is:
How do we get some testing coverage of -stable kernels by users to catch 
issues?
And compile errors are the least of my worries.

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

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