kernel-testers.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Edwin van den Oetelaar (via gmail.com)"  <oetelaar.automatisering-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Kernel Testers List
	<kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: 2.6.29.1 to 2.6.30rc1 upgrade breaks my hotplug (and how I fixed it)
Date: Wed, 08 Apr 2009 17:00:56 +0200	[thread overview]
Message-ID: <49DCBC28.5070301@gmail.com> (raw)

Someone changed
/lib/kobject_uevent.c

To do stuff more parallel,

@@ -248,7 +258,7 @@
                        goto exit;

                retval = call_usermodehelper(argv[0], argv,
-                                            env->envp, UMH_WAIT_EXEC);
+                                            env->envp, UMH_NO_WAIT);
        }

This breaks my hotplug, it only gets called once about every 500 events.
Changing UMH_NO_WAIT back to UMH_WAIT_EXEC again fixed my hotplug problems.

I used i686 kernel with /sbin/mdev handler (busybox system)
gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)


Best regards,
Edwin van den Oetelaar (Netherlands)

                 reply	other threads:[~2009-04-08 15:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=49DCBC28.5070301@gmail.com \
    --to=oetelaar.automatisering-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).