From: Sean MacLennan <smaclennan@pikatech.com>
To: "linuxppc-dev" <linuxppc-dev@ozlabs.org>
Subject: Re: Hotplug on PPC4xx
Date: Tue, 7 Apr 2009 19:27:28 -0400 [thread overview]
Message-ID: <20090407192728.7218eea9@lappy.seanm.ca> (raw)
In-Reply-To: <20090406182023.0729073a@lappy.seanm.ca>
On Mon, 6 Apr 2009 18:20:23 -0400
"Sean MacLennan" <sean.maclennan@ottawa.kanatek.ca> wrote:
> I am trying to run the /sbin/hotplug from the kernel and it doesn't
> work. Has anybody got it running?
I looked into it some more. It turns out that the env pointers are
freed before they are copied.
In kobject_uevent_env() if I change the line that calls the helper from
UMH_NO_WAIT to UMH_WAIT_EXEC, then it works... but probably at a loss
of performance.
retval = call_usermodehelper(argv[0], argv,
env->envp, UMH_WAIT_EXEC);
Any other ideas?
Cheers,
Sean
next prev parent reply other threads:[~2009-04-07 23:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-06 22:20 Hotplug on PPC4xx Sean MacLennan
2009-04-07 23:27 ` Sean MacLennan [this message]
2009-04-08 0:27 ` Michael Ellerman
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=20090407192728.7218eea9@lappy.seanm.ca \
--to=smaclennan@pikatech.com \
--cc=linuxppc-dev@ozlabs.org \
/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;
as well as URLs for NNTP newsgroup(s).