From: Andrew Morton <akpm@linux-foundation.org>
To: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Cc: paulmck@linux.vnet.ibm.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH for 2.6.25] Markers - use synchronize_sched()
Date: Tue, 1 Apr 2008 13:30:17 -0700 [thread overview]
Message-ID: <20080401133017.9484a35b.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080331131609.GA22207@Krystal>
On Mon, 31 Mar 2008 09:16:09 -0400
Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca> wrote:
> Use synchronize_sched before calling call_rcu in CONFIG_PREEMPT_RCU until we
> have call_rcu_sched and rcu_barrier_sched in mainline. It will slow down the
> marker operations in CONFIG_PREEMPT_RCU, but it fixes the current race against
> the preempt_disable/enable() protected code paths.
A better changelog would have described the bug which is being fixed.
> Paul, is this ok ? It would be good to get this in for 2.6.25 final.
Paul seems to have nodded off. I'll merge it.
next prev parent reply other threads:[~2008-04-01 20:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-31 13:16 [PATCH for 2.6.25] Markers - use synchronize_sched() Mathieu Desnoyers
2008-04-01 20:30 ` Andrew Morton [this message]
2008-04-01 20:45 ` Paul E. McKenney
2008-04-01 22:25 ` Mathieu Desnoyers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080401133017.9484a35b.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=paulmck@linux.vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox