| 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
| ||
|
Date: Thu, 28 May 2015 17:05:42 -0400 From: Steven Rostedt <rostedt@...dmis.org> To: Dan Streetman <ddstreet@...e.org> Cc: Andrew Morton <akpm@...ux-foundation.org>, "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>, Josh Triplett <josh@...htriplett.org>, Mathieu Desnoyers <mathieu.desnoyers@...icios.com>, Lai Jiangshan <laijs@...fujitsu.com>, linux-kernel@...r.kernel.org Subject: Re: [PATCH 1/2] rcu: introduce list_last_or_null_rcu On Thu, 28 May 2015 16:35:27 -0400 Dan Streetman <ddstreet@...e.org> wrote: > Add list_last_or_null_rcu(), to simplify getting the last entry from a > rcu-protected list. The standard list_last_entry() can't be used as it > is not rcu-protected; the list may be modified concurrently. And the > ->prev pointer can't be used, as only the ->next pointers are protected > by rcu. > > This simply iterates forward through the entire list, to get to the last > entry. If the list is empty, it returns NULL. May I asked what this would be used for? It seems awfully inefficient in its implementation. What use cases would this be for? I hate to add something like this as a generic function which would encourage people to use it. Iterating over an entire list to find the last element is just nasty. -- Steve -- 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/
Powered by blists - more mailing lists