linux-kernel - Re: 2.6.19-rc2-mm2

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:	Sun, 22 Oct 2006 23:18:21 +0100
From:	Andy Whitcroft <apw@...dowen.org>
To:	"Martin J. Bligh" <mbligh@...igh.org>
CC:	Andrew Morton <akpm@...l.org>, linux-kernel@...r.kernel.org,
	Badari Pulavarty <pbadari@...ibm.com>,
	Greg Kroah-Hartman <gregkh@...e.de>
Subject: Re: 2.6.19-rc2-mm2

Martin J. Bligh wrote:
> Martin J. Bligh wrote:
>> Andrew Morton wrote:
>>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.19-rc2/2.6.19-rc2-mm2/
>>>
>>>
>>> - Added the IOAT tree as git-ioat.patch (Chris Leech)
>>>
>>> - I worked out the git magic to make the wireless tree work
>>>   (git-wireless.patch).  Hopefully it will be in -mm more often now.
>>
>> I think the IO & fsx problems have got better, but this one is still
>> broken, at least.
>>
>> See end of fsx runlog here:
>>
>> http://test.kernel.org/abat/57486/debug/test.log.1
>>
>> which looks like this:
>>
>> Total Test PASSED: 79
>> Total Test FAILED: 3
>>   139 ./fsx-linux -N 10000 -o 8192 -A -l 500000 -r 1024 -t 2048 -w
>> 2048 -Z -R -W test/junkfile
>>   139 ./fsx-linux -N 10000 -o 128000 -r 2048 -w 4096 -Z -R -W
>> test/junkfile
>>   139 ./fsx-linux -N 10000 -o 8192 -A -l 500000 -r 1024 -t 2048 -w
>> 1024 -Z -R -W test/junkfile
>> Failed rc=1
>> 10/20/06-02:41:55 command complete: (1) rc=1 (TEST FAIL)
> 
> On further examination ... and rather more worryingly, this started
> between 2.6.18 and 2.6.18.1. I don't see any reiserfs patches in
> there, and possibly it's a machine config change? But rather worrying.
> 
> Where do the changelogs for the stable release kernels sit again?

Ok, as has been said there are changes in the tests which make error
detection better, which means we cannot be sure this _is_ new.  The
logical way to eliminate that is to rerun the 2.6.18 test again to see
if it gains the problem.

I'll queue one up.

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