| 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
| ||
|
Message-ID: <4551BABE.1060307@steudten.com>
Date: Wed, 08 Nov 2006 12:08:46 +0100
From: "alpha @ steudten Engineering" <NWQ3MzhlY2QwZDAzODVhN@...udten.com>
To: linux-kernel@...r.kernel.org, linux-alpha@...r.kernel.org
Subject: Re: INFO alpha CPU: Locking API testsuite: Results kernel 2.6.18.1
CONFIG_PROVE_LOCKING=y ?
It't not there/set! It depends on:
config PROVE_LOCKING
bool "Lock debugging: prove locking correctness"
depends on DEBUG_KERNEL && TRACE_IRQFLAGS_SUPPORT && STACKTRACE_SUPPORT && LOCKDEP_SUPPORT
select LOCKDEP
so it looks like only DEBUG_KERNEL is set for alpha.
Maybe some dependencies are missing.. I'll check this.
Jarek Poplawski wrote:
> On 04-11-2006 15:27, alpha @ steudten Engineering wrote:
>> kernel-2.6.18.1 ALPHA SX164
>> No "failed" on x86.
>> ------------------------
>> | Locking API testsuite:
>> ----------------------------------------------------------------------------
>> | spin |wlock |rlock |mutex | wsem | rsem |
>> --------------------------------------------------------------------------
>> A-A deadlock:failed|failed| ok |failed|failed|failed|
> ...
>> --------------------------------------------------------
>> 143 out of 218 testcases failed, as expected. |
>> ----------------------------------------------------
>
> CONFIG_PROVE_LOCKING=y ?
-
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/
Powered by blists - more mailing lists