Re: Locking API testsuite: Failures

[Peter Zijlstra]

On Wed, 2008-08-27 at 08:27 +0800, Peter Teoh wrote:
> [    0.000999] | Locking API testsuite:
> [    0.000999] ----------------------------------------------------------------------------
> [    0.000999]                                  | spin |wlock |rlock
> |mutex | wsem | rsem |
> [    0.000999]
> --------------------------------------------------------------------------
> [    0.000999]                      A-A deadlock:failed|failed|  ok
> |failed|failed|failed|
> [    0.000999]                  A-B-B-A deadlock:failed|failed|  ok
> |failed|failed|failed|
> [    0.000999]              A-B-B-C-C-A deadlock:failed|failed|  ok
> |failed|failed|failed|
> [    0.000999]              A-B-C-A-B-C deadlock:failed|failed|  ok
> |failed|failed|failed|
> [    0.000999]          A-B-B-C-C-D-D-A deadlock:failed|failed|  ok
> |failed|failed|failed|
> [    0.000999]          A-B-C-D-B-D-D-A deadlock:failed|failed|  ok
> |failed|failed|failed|
> [    0.000999]          A-B-C-D-B-C-D-A deadlock:failed|failed|  ok
> |failed|failed|failed|
> [    0.000999]                     double
> unlock:failed|failed|failed|failed|failed|failed|
> [    0.000999]                   initialize
> held:failed|failed|failed|failed|failed|failed|
> [    0.000999]                  bad unlock order:  ok  |  ok  |  ok  |
>  ok  |  ok  |  ok  |
> [    0.000999]
> --------------------------------------------------------------------------
> [    0.000999]               recursive read-lock:             |  ok  |
>             |failed|
> [    0.000999]            recursive read-lock #2:             |  ok  |
>             |failed|
> [    0.000999]             mixed read-write-lock:             |failed|
>             |failed|
> [    0.000999]             mixed write-read-lock:             |failed|
>             |failed|
> [    0.000999]
> --------------------------------------------------------------------------
> [    0.000999]      hard-irqs-on + irq-safe-A/12:failed|failed|  ok  |
> [    0.000999]      soft-irqs-on + irq-safe-A/12:failed|failed|  ok  |
> [    0.000999]      hard-irqs-on + irq-safe-A/21:failed|failed|  ok  |
> [    0.000999]      soft-irqs-on + irq-safe-A/21:failed|failed|  ok  |
> [    0.000999]        sirq-safe-A => hirqs-on/12:failed|failed|  ok  |
> [    0.000999]        sirq-safe-A => hirqs-on/21:failed|failed|  ok  |
> [    0.000999]          hard-safe-A + irqs-on/12:failed|failed|  ok  |
> [    0.000999]          soft-safe-A + irqs-on/12:failed|failed|  ok  |
> [    0.000999]          hard-safe-A + irqs-on/21:failed|failed|  ok  |
> [    0.000999]          soft-safe-A + irqs-on/21:failed|failed|  ok  |
> [    0.000999]     hard-safe-A + unsafe-B #1/123:failed|failed|  ok  |
> [    0.000999]     soft-safe-A + unsafe-B #1/123:failed|failed|  ok  |
> 
> truncated....
> 
> I am just curious what does all these failures imply?

Probably that you forgot to enable lockdep ;-)

In which case the error cases fail to produce an error, and the test
fails, but its an expected error, otherwise it would have shouted much
more verbose.



--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/