[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1207084480.29991.2.camel@lappy>
Date: Tue, 01 Apr 2008 23:14:40 +0200
From: Peter Zijlstra <a.p.zijlstra@...llo.nl>
To: Christoph Lameter <clameter@....com>
Cc: Hugh Dickins <hugh@...itas.com>,
Andrea Arcangeli <andrea@...ranet.com>,
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [patch 1/9] EMM Notifier: The notifier calls
(Christoph, why are your CCs so often messed up?)
On Tue, 2008-04-01 at 13:55 -0700, Christoph Lameter wrote:
> plain text document attachment (emm_notifier)
> +/* Register a notifier */
> +void emm_notifier_register(struct emm_notifier *e, struct mm_struct *mm)
> +{
> + e->next = mm->emm_notifier;
> + /*
> + * The update to emm_notifier (e->next) must be visible
> + * before the pointer becomes visible.
> + * rcu_assign_pointer() does exactly what we need.
> + */
> + rcu_assign_pointer(mm->emm_notifier, e);
> +}
> +EXPORT_SYMBOL_GPL(emm_notifier_register);
> +
> +/* Perform a callback */
> +int __emm_notify(struct mm_struct *mm, enum emm_operation op,
> + unsigned long start, unsigned long end)
> +{
> + struct emm_notifier *e = rcu_dereference(mm)->emm_notifier;
> + int x;
> +
> + while (e) {
> +
> + if (e->callback) {
> + x = e->callback(e, mm, op, start, end);
> + if (x)
> + return x;
> + }
> + /*
> + * emm_notifier contents (e) must be fetched after
> + * the retrival of the pointer to the notifier.
> + */
> + e = rcu_dereference(e)->next;
> + }
> + return 0;
> +}
> +EXPORT_SYMBOL_GPL(__emm_notify);
> +#endif
Those rcu_dereference()s are wrong. They should read:
e = rcu_dereference(mm->emm_notifier);
and
e = rcu_dereference(e->next);
--
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