public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: nhorman@mail.tuxdriver.com
To: "Andi Kleen" <andi@firstfloor.org>,
	"Neil Horman" <nhorman@tuxdriver.com>
Cc: "Mel Gorman" <mel@csn.ul.ie>,
	akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
	"Andi Kleen" <andi@firstfloor.org>,
	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Subject: Re: mmotm 2010-03-09-19-15: Lot of scheduling while atomic warnings related to RCU
Date: Thu, 11 Mar 2010 19:09:35 -0500	[thread overview]
Message-ID: <E1NpsRW-0006gl-Cm@smtp.tuxdriver.com> (raw)
In-Reply-To: <20100311223048.GI20695@one.firstfloor.org>


On Thu, 11 Mar 2010 17:30:48 -0500, Andi Kleen wrote:
> > a/lib/kobject_uevent.c~sysctl-fix-up-remaining-references-to-uevent_helper-fix
> > +++ a/lib/kobject_uevent.c
> > @@ -273,10 +273,11 @@ int kobject_uevent_env(struct kobject *k
> >  #endif
> > 
> >         /* call uevent_helper, usually only enabled during early boot */
> > +       rcu_read_lock();
> >         helper = rcu_dereference(uevent_helper);
> >         if (helper[0])
> >                 retval = uevent_call_helper(subsystem, env);
> > -
> > +       rcu_read_unlock();
> >  exit:
> 
> The data actually has to be copied, there's a helper for this in rcustring.
> I'll try to send a patch later.
> 
> > loads/unloads while changing uevent_helper.  Anywho, should be easy to fix,
> > Mel, can you modify the code to copy helper to a private variable, then unlock
> > the rcu read side prior to calling uevent_call_helper?  I imagine that would be
> 
> Yes, except rcustring already has a helper for that :)
> 
Yes but the rcustring bits all got reverted, trashing my series :), so its all got to be rediffed anyway

Neil
> -Andi
> 


  reply	other threads:[~2010-03-12  0:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-10  3:16 mmotm 2010-03-09-19-15 uploaded akpm
2010-03-10 19:43 ` [PATCH -mmotm] leds: fix net5501 kconfig Randy Dunlap
2010-03-10 19:57 ` mmotm 2010-03-09-19-15: Lot of scheduling while atomic warnings related to RCU Mel Gorman
2010-03-10 20:21   ` Andrew Morton
2010-03-10 20:34     ` Mel Gorman
2010-03-10 20:32   ` Neil Horman
2010-03-11 22:30     ` Andi Kleen
2010-03-12  0:09       ` nhorman [this message]
2010-03-12 11:46     ` Mel Gorman
2010-03-12 15:29       ` Neil Horman
2010-03-12 15:41         ` Mel Gorman

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=E1NpsRW-0006gl-Cm@smtp.tuxdriver.com \
    --to=nhorman@mail.tuxdriver.com \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mel@csn.ul.ie \
    --cc=nhorman@tuxdriver.com \
    --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