linux-kernel - Re: [PATCH v7 2/2] 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]

Date:	Thu, 7 Aug 2014 11:58:35 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Waiman Long <Waiman.Long@...com>
Cc:	Ingo Molnar <mingo@...nel.org>,
	Maarten Lankhorst <maarten.lankhorst@...onical.com>,
	Rik van Riel <riel@...hat.com>, linux-kernel@...r.kernel.org,
	Scott J Norton <scott.norton@...com>,
	Fengguang Wu <fengguang.wu@...el.com>
Subject: Re: [PATCH v7 2/2] locking/selftest: Support queued rwlock

On Wed, Aug 06, 2014 at 01:22:02PM -0400, Waiman Long wrote:
> The queued rwlock does not support the use of recursive read-lock in
> the process context. With changes in the lockdep code to check and
> disallow recursive read-lock, it is also necessary for the locking
> selftest to be updated to change the process context recursive read
> locking results from SUCCESS to FAILURE for rwlock.
> +static void rlock_AHA1(void)
> +{
> +	RL(X1);
> +	HARDIRQ_ENTER();
> +	RL(X1);	// this one should NOT fail
> +	HARDIRQ_EXIT();
> +}
> +
> +static void rlock_AHA1B(void)
> +{
> +	RL(X1);
> +	HARDIRQ_ENTER();
> +	RL(X2);	// this one should NOT fail
> +	HARDIRQ_EXIT();
> +}
> +
> +static void rlock_ASAHA1(void)
> +{
> +	RL(X1);
> +	SOFTIRQ_ENTER();
> +	RL(X1);	// this one should NOT fail
> +	HARDIRQ_ENTER();
> +	RL(X1);	// this one should NOT fail
> +	HARDIRQ_EXIT();
> +	SOFTIRQ_EXIT();
>  }

Thanks!

Content of type "application/pgp-signature" skipped