From: paulmck@linux.vnet.ibm.com (Paul E. McKenney)
Subject: [ltt-dev] [PATCH 6/7] urcu, call_rcu: Cleanup call_rcu_data pointers before used in child
Date: Thu, 29 Sep 2011 11:08:25 -0700 [thread overview]
Message-ID: <20110929180825.GH2362@linux.vnet.ibm.com> (raw)
In-Reply-To: <20110929175912.GB7066@Krystal>
On Thu, Sep 29, 2011 at 01:59:12PM -0400, Mathieu Desnoyers wrote:
> * Paul E. McKenney (paulmck at linux.vnet.ibm.com) wrote:
> > On Wed, Sep 28, 2011 at 04:34:32PM +0800, Lai Jiangshan wrote:
> > > Signed-off-by: Lai Jiangshan <laijs at cn.fujitsu.com>
> > > ---
> > > urcu-call-rcu-impl.h | 6 ++++++
> > > 1 files changed, 6 insertions(+), 0 deletions(-)
> > >
> > > diff --git a/urcu-call-rcu-impl.h b/urcu-call-rcu-impl.h
> > > index 65c1c7a..3c68ae7 100644
> > > --- a/urcu-call-rcu-impl.h
> > > +++ b/urcu-call-rcu-impl.h
> > > @@ -686,6 +686,12 @@ void call_rcu_after_fork_child(void)
> > > default_call_rcu_data = NULL;
> > > (void)get_default_call_rcu_data();
> > >
> > > + /* Cleanup call_rcu_data pointers before used */
> > > + maxcpus = 0;
> > > + free(per_cpu_call_rcu_data);
> > > + per_cpu_call_rcu_data = NULL;
> >
> > Good catch! I would expect that the number of CPUs would be the
> > same for the child as it was for the parent, but doesn't hurt to
> > make the child start over.
> >
> > > + thread_call_rcu_data = NULL;
> >
> > Isn't thread_call_rcu_data already NULL due to the child being a new
> > thread and the C initialization-to-zero rules?
>
> #include <unistd.h>
> #include <stdio.h>
>
> int __thread a;
>
> int main()
> {
> int pid;
>
> a = 1;
> pid = fork();
> if (pid > 0) {
> printf("parent val %d\n", a);
> return 0;
> } else {
> printf("child val %d\n", a);
> return 0;
> }
> }
>
> compudj at thinkos:/tmp$ gcc -o test test.c
> compudj at thinkos:/tmp$ ./test
> parent val 1
> child val 1
>
> AFAIK, the c initialization to zero rules apply to exec(), not fork.
> Here we are taking care of after-fork in the child, in cases where the
> child is not doing an exec.
>
> Does that make more sense ?
I would think that the forked child would be a new thread, but obviously
not! I stand corrected.
Thanx, Paul
> Thanks,
>
> Mathieu
>
>
> >
> > Thanx, Paul
> >
> > > +
> > > /* Dispose of all of the rest of the call_rcu_data structures. */
> > > cds_list_for_each_entry_safe(crdp, next, &call_rcu_data_list, list) {
> > > if (crdp == default_call_rcu_data)
> > > --
> > > 1.7.4.4
> > >
>
> --
> Mathieu Desnoyers
> Operating System Efficiency R&D Consultant
> EfficiOS Inc.
> http://www.efficios.com
>
next prev parent reply other threads:[~2011-09-29 18:08 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-28 8:34 [ltt-dev] [PATCH 0/7] urcu,call_rcu: minior fixes, round2 Lai Jiangshan
2011-09-28 8:34 ` [ltt-dev] [PATCH 1/7] urcu, call_rcu: protects call_rcu_data_list when remove node Lai Jiangshan
2011-09-29 17:00 ` Mathieu Desnoyers
2011-09-28 8:34 ` [ltt-dev] [PATCH 2/7] urcu, defer_rcu: fix missing respond to a cancellation request Lai Jiangshan
2011-09-29 17:13 ` Mathieu Desnoyers
2011-09-28 8:34 ` [ltt-dev] [PATCH 3/7] urcu, defer_rcu: Avoid thread exit unexpected Lai Jiangshan
2011-09-29 17:27 ` Mathieu Desnoyers
2011-09-28 8:34 ` [ltt-dev] [PATCH 4/7] urcu, defer_rcu: Simplify defer_rcu() encoding Lai Jiangshan
2011-09-29 17:49 ` Mathieu Desnoyers
2011-09-28 8:34 ` [ltt-dev] [PATCH 5/7] urcu, call_rcu: avoid create call_rcu_data for child when unneed Lai Jiangshan
2011-09-29 17:27 ` Paul E. McKenney
2011-09-29 17:52 ` Mathieu Desnoyers
2011-09-28 8:34 ` [ltt-dev] [PATCH 6/7] urcu, call_rcu: Cleanup call_rcu_data pointers before used in child Lai Jiangshan
2011-09-29 17:37 ` Paul E. McKenney
2011-09-29 17:59 ` Mathieu Desnoyers
2011-09-29 18:08 ` Paul E. McKenney [this message]
2011-09-29 18:19 ` Mathieu Desnoyers
2011-09-29 18:29 ` Paul E. McKenney
2011-09-29 18:28 ` Mathieu Desnoyers
2011-09-29 19:43 ` Mathieu Desnoyers
2011-09-29 19:53 ` Mathieu Desnoyers
2011-09-28 8:34 ` [ltt-dev] [PATCH 7/7] urcu, call_rcu: Array initialized before pointer is planted Lai Jiangshan
2011-09-29 17:33 ` Paul E. McKenney
2011-09-29 20:07 ` Mathieu Desnoyers
2011-09-29 21:13 ` 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=20110929180825.GH2362@linux.vnet.ibm.com \
--to=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