linux-kernel - Re: 2.6.19-rc1-mm1

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: <4533ABB3.1070104@shadowen.org>
Date:	Mon, 16 Oct 2006 16:56:35 +0100
From:	Andy Whitcroft <apw@...dowen.org>
To:	Badari Pulavarty <pbadari@...ibm.com>
CC:	"Martin J. Bligh" <mbligh@...gle.com>,
	Andrew Morton <akpm@...l.org>, linux-kernel@...r.kernel.org
Subject: Re: 2.6.19-rc1-mm1

Badari Pulavarty wrote:
> Martin J. Bligh wrote:
>> Andrew Morton wrote:
>>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.19-rc1/2.6.19-rc1-mm1/
>>>
>>>
>>>
>>>
>>>   
>> fsx seems to fail now, across several different machines.
>>
>> http://test.kernel.org/functional/index.html
>>
>>
>> and drill down under "regression" on the failing ones.
>>
>> eg, see end of
>> http://test.kernel.org/abat/54516/debug/test.log.1 (i386)
>> and
>> http://test.kernel.org/abat/54503/debug/test.log.1 (x86_64)
>>
> 
> I am seeing fsx failures on 1k/2k ext3 filesystems, but not on 4k.
> Do you know the filesystem type & blocksize ?

Ok.  I've been poking at these results to try and get you these answers.
 In the process I noted that the benchmark was recently reviewed and
overhauled.  Looking at the changes it looks like we are now reporting
the results from some tests which are backgrounded for additional load,
which would not have previously been reported.  So this might not be a
new phenomenon.  We have some stable tests coming through now, so I
should be able to use them as a reference to be sure.

Here are the ones which are failing currently, note that the 139 at the
start is the exit status as reported by the shell, so SIGSEGV:

bl6-13: x86_64 ext3
-------------------
139 ./fsx-linux -l 500000 -r 4096 -t 2048 -w 2048 -Z -R -W -N 10000
test/junkfile
139 ./fsx-linux -N 10000 -o 128000 -A -l 500000 -r 512 -t 4096 -w 1024
-Z -R -W test/junkfile


elm3b239: x86_64 reiserfs
-------------------------
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

I have also seen the following style messages on 19-rc1-mm1:

short write: 0x15000 bytes instead of 0xf000

Note that this really does mean a _long_ write!

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