linux-kernel - Re: [RFC PATCH 1/5] Move task's RCU code to rcupdate.h

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: <1301571096.4859.243.camel@twins>
Date:	Thu, 31 Mar 2011 13:31:36 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Lai Jiangshan <laijs@...fujitsu.com>
Cc:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
	Ingo Molnar <mingo@...e.hu>,
	Dipankar Sarma <dipankar@...ibm.com>,
	Jan Beulich <jbeulich@...ell.com>,
	David Howells <dhowells@...hat.com>,
	Alexander van Heukelum <heukelum@...tmail.fm>,
	"H. Peter Anvin" <hpa@...ux.intel.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Roland McGrath <roland@...hat.com>,
	Oleg Nesterov <oleg@...hat.com>,
	Serge Hallyn <serue@...ibm.com>, linux-kernel@...r.kernel.org,
	Christoph Lameter <clameter@....com>,
	Sam Ravnborg <sam@...nborg.org>
Subject: Re: [RFC PATCH 1/5] Move task's RCU code to rcupdate.h

On Mon, 2011-03-28 at 10:58 +0800, Lai Jiangshan wrote:
> +struct task_rcu_struct {
> +#ifdef CONFIG_PREEMPT_RCU
> +       int rcu_read_lock_nesting;
> +       char rcu_read_unlock_special;

Is there a good reason that's a char? It'll leave a 3 byte hole in this
location.

> +       struct list_head rcu_node_entry;
> +#ifdef CONFIG_TREE_PREEMPT_RCU
> +       struct rcu_node *rcu_blocked_node;
> +#endif /* #ifdef CONFIG_TREE_PREEMPT_RCU */
> +#ifdef CONFIG_RCU_BOOST
> +       struct rt_mutex *rcu_boost_mutex;
> +#endif /* #ifdef CONFIG_RCU_BOOST */
> +#endif /* #ifdef CONFIG_PREEMPT_RCU */
> +}; 
--
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/