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]

Message-ID: <453907D5.8070501@shadowen.org>
Date:	Fri, 20 Oct 2006 18:31:01 +0100
From:	Andy Whitcroft <apw@...dowen.org>
To:	Badari Pulavarty <pbadari@...ibm.com>
CC:	"Martin J. Bligh" <mbligh@...igh.org>,
	Andrew Morton <akpm@...l.org>, linux-kernel@...r.kernel.org
Subject: Re: 2.6.19-rc2-mm2

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-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)
>>
> I see following message in the log which makes me think the reiserfs
> tail handling with DIO problem...
> Is this reiserfs ? Chris Mason told me that we need to use -onotail
> mount option for this to pass.
> Not sure why we haven't see this before...
> 
> doread: read: Invalid argument

/dev/sda1 / reiserfs rw 0 0

Yes, this is a reiserfs filesystem we are testing on.  This is a new
machine and probabally the only one reporting to TKO with reiserfs as
its root filesystem.

Can you explain what difference this option makes, and why it is
changing the visible semantics of the filesystem?  Is this valid?

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