From: Oleg Nesterov <oleg@tv-sign.ru>
To: Eric Dumazet <dada1@cosmosbay.com>
Cc: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Dipankar Sarma <dipankar@in.ibm.com>,
Andrew Morton <akpm@osdl.org>,
Alan Stern <stern@rowland.harvard.edu>,
linux-kernel@vger.kernel.org
Subject: Re: PATCH? rcu_do_batch: fix a pure theoretical memory ordering race
Date: Mon, 4 Dec 2006 01:12:27 +0300 [thread overview]
Message-ID: <20061203221227.GA468@oleg> (raw)
In-Reply-To: <457334C4.8010604@cosmosbay.com>
On 12/03, Eric Dumazet wrote:
>
> Oleg Nesterov a ?crit :
>
> Yes, but how is it related to RCU ?
> I mean, rcu_do_batch() is just a loop like others in kernel.
> The loop itself is not buggy, but can call a buggy function, you are right.
int start_me_again;
struct rcu_head rcu_head;
void rcu_func(struct rcu_head *rcu)
{
start_me_again = 1;
}
// could be called on arbitrary CPU
void check_start_me_again(void)
{
static spinlock_t lock;
spin_lock(lock);
if (start_me_again) {
start_me_again = 0;
call_rcu(&rcu_head, rcu_func);
}
spin_unlock(lock);
}
I'd say this code is not buggy.
In case it was not clear. I do not claim we need this patch (I don't know).
And yes, I very much doubt we can hit this problem in practice (even if I am
right).
What I don't agree with is that it is callback which should take care of this
problem.
> A smp_rmb() wont avoid all possible bugs...
For example?
Oleg.
next prev parent reply other threads:[~2006-12-03 22:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-02 21:25 PATCH? rcu_do_batch: fix a pure theoretical memory ordering race Oleg Nesterov
2006-12-03 17:34 ` Eric Dumazet
2006-12-03 20:01 ` Oleg Nesterov
2006-12-03 20:34 ` Eric Dumazet
2006-12-03 22:12 ` Oleg Nesterov [this message]
2006-12-03 23:08 ` Eric Dumazet
2006-12-03 23:46 ` Oleg Nesterov
2006-12-04 16:43 ` Paul E. McKenney
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=20061203221227.GA468@oleg \
--to=oleg@tv-sign.ru \
--cc=akpm@osdl.org \
--cc=dada1@cosmosbay.com \
--cc=dipankar@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=stern@rowland.harvard.edu \
/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