linux-kernel - Re: locking: Add kselftests for ww

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] [day] [month] [year] [list]

Date:   Wed, 22 Feb 2017 15:29:47 +0100
From:   Geert Uytterhoeven <geert@...ux-m68k.org>
To:     Chris Wilson <chris@...is-wilson.co.uk>
Cc:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: locking: Add kselftests for ww_mutex

Hi Chris,

On Thu, Dec 1, 2016 at 12:47 PM, Chris Wilson <chris@...is-wilson.co.uk> wrote:
> Nicolai Hähnle was looking into a deadlock within ww_mutexes (that has
> been fixed by Peter's mutex rewrite) and to support his changes, I
> thought it was be useful to have a small validation suite for ww_mutex.

How long do these selftests typically take?
Do they need multiple CPU cores, lots of memory?
I.e. after how much time without any output should I start to worry
(on an emulated
Atari running Linux/m68k ;-)?

Thanks!

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds