linux-kernel - Re: [PATCH 10/10] Get rid of ipc_lock

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: <20080501043324.GI30274@tpepper-t42p.dolavim.us>
Date:	Wed, 30 Apr 2008 21:33:25 -0700
From:	Tim Pepper <lnxninja@...ux.vnet.ibm.com>
To:	Nadia.Derbey@...l.net
Cc:	manfred@...orfullife.com, paulmck@...ux.vnet.ibm.com,
	linux-kernel@...r.kernel.org, efault@....de,
	akpm@...ux-foundation.org
Subject: Re: [PATCH 10/10] Get rid of ipc_lock_down()

On Tue 29 Apr at 16:33:14 +0200 Nadia.Derbey@...l.net said:
> [PATCH 10/10]
> 
> With the previous patch ipc_lock() becomes lockless.
> So there is no need anymore for ipc_lock_down()-like routines.

...cleanup post conversion to RCU.

Could we get a version of the series without all the duplication and
without the cleanups (separate into standalone pre- and post- patches)?
If you're too busy, now that I've sifted through these I could make a
simpler series that does this.

It will be a looooot easier to discuss the locking when all we're looking
at is the locking changes.

-- 
Tim Pepper  <lnxninja@...ux.vnet.ibm.com>
IBM Linux Technology Center
--
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/