linux-kernel - Re: [PATCH 04/11] ipc: move locking out of ipcctl_pre_down

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <m2vc6i3j3j.fsf@firstfloor.org>
Date:	Thu, 16 May 2013 10:55:28 -0700
From:	Andi Kleen <andi@...stfloor.org>
To:	Davidlohr Bueso <davidlohr.bueso@...com>
Cc:	akpm@...ux-foundation.org, torvalds@...ux-foundation.org,
	riel@...hat.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 04/11] ipc: move locking out of ipcctl_pre_down_nolock

Davidlohr Bueso <davidlohr.bueso@...com> writes:

> This function currently acquires both the rw_mutex and the rcu lock on
> successful lookups, leaving the callers to explicitly unlock them, creating
> another two level locking situation.

Note that the rcu read lock is not a real lock, so it doesn't have the
usual ordering problems.

-Andi

-- 
ak@...ux.intel.com -- Speaking for myself only
--
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/