linux-kernel - [PATCH -mm 0/3] percpu_rw_semaphore: lockdep + config

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

Date:	Sun, 18 Nov 2012 20:02:57 +0100
From:	Oleg Nesterov <oleg@...hat.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Anton Arapov <anton@...hat.com>, Ingo Molnar <mingo@...e.hu>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Michal Marek <mmarek@...e.cz>,
	Mikulas Patocka <mpatocka@...hat.com>,
	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
	Peter Zijlstra <peterz@...radead.org>,
	Srikar Dronamraju <srikar@...ux.vnet.ibm.com>,
	linux-kernel@...r.kernel.org
Subject: [PATCH -mm 0/3] percpu_rw_semaphore: lockdep + config

On 11/11, Oleg Nesterov wrote:
>
> To remind, once/if I am sure you agree with this patch I'll send 2 additional
> and simple patches:
>
> 	1. lockdep annotations
>
> 	2. CONFIG_PERCPU_RWSEM

It turns out, lockdep annotations are not that simple due to internal
locks used by percpu_rw_semaphore. To clarify, it is actually simple
but lockdep_set_novalidate_class() doesn't seem to actually work, and
more importantly, it must not be used according to checkpatch.pl. And
I guess ->lockdep_recursion should not be used too.

However, without some tricks, the output from lockdep (when it finds
the problem) does not look very clear because it blames those internal
locks instead of "the whole" percpu_rw_semaphore.

So this series starts with the small optimization which I was going to
do later. It removes ->writer_mutex and greatly simplifies 2/3.

Oleg.

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