linux-kernel - Re: [PATCH 2/2 v6] locking/selftest: Support queued rwlock

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: <CAKocOOMa89+Ej0rk-LyQLBcwDvLtsXq7x+oPwBMS1N61kKUwQg@mail.gmail.com>
Date:	Tue, 5 Aug 2014 08:07:28 -0600
From:	Shuah Khan <shuahkhan@...il.com>
To:	Peter Zijlstra <peterz@...radead.org>,
	Greg KH <gregkh@...uxfoundation.org>
Cc:	Waiman Long <Waiman.Long@...com>, Ingo Molnar <mingo@...nel.org>,
	Maarten Lankhorst <maarten.lankhorst@...onical.com>,
	Rik van Riel <riel@...hat.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Scott J Norton <scott.norton@...com>,
	Fengguang Wu <fengguang.wu@...el.com>
Subject: Re: [PATCH 2/2 v6] locking/selftest: Support queued rwlock

On Tue, Aug 5, 2014 at 7:28 AM, Peter Zijlstra <peterz@...radead.org> wrote:

> Maybe I wasn't clear; but I meant you should extend the lock tests to
> cover the full qrwlock semantics.
>
> That means we also need tests like:
>
>         RL(X1);
>         IRQ_ENTER();
>         RL(X2);
>         IRQ_EXIT();
>
> To fully validate that in_interrupt exception to fairness etc..

A bit off topic for this patch, however relevant for tests in general.
Is there a reason why these locking selftests need to be under lib?
Can they be consolidated under tools/testing/selftests?

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