public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew <cmkrnl@speakeasy.net>
To: greg@kroah.com, linux-kernel@vger.kernel.org
Subject: [PATCH] kernel-2.6.9.rc4 lib/kobject.c
Date: Sat, 16 Oct 2004 23:47:44 -0400	[thread overview]
Message-ID: <4171EB60.50800@speakeasy.net> (raw)



There are two conditions where kset_hotplug can exit without the call to 
call_usermodehelper() after incrementing the sequence_number.  This 
patch eliminates the first by getting the kobj_path before the 
sequence_number++. It also reduces the likelihood of the second by 
decrementing the sequence_number (if it can) if the call to 
kset->hotplug_ops->hotplug() fails.

Some user space programs (rightly or wrongly) are expecting there would 
be no "gaps" in hotplug event sequence numbers, and hang waiting for the 
"missing" events.


   Signed-off-by: Andrew Duggan <cmkrnl@speakeasy.net>



--- lib/kobject.c.orig    2004-10-16 20:51:01.450973973 -0400
+++ lib/kobject.c    2004-10-16 21:08:19.961602269 -0400
@@ -177,6 +177,10 @@ static void kset_hotplug(const char *act
    envp [i++] = scratch;
    scratch += sprintf(scratch, "ACTION=%s", action) + 1;

+    kobj_path = kobject_get_path(kset, kobj, GFP_KERNEL);
+    if (!kobj_path)
+        goto exit;
+
    spin_lock(&sequence_lock);
    seq = sequence_num++;
    spin_unlock(&sequence_lock);
@@ -184,10 +188,6 @@ static void kset_hotplug(const char *act
    envp [i++] = scratch;
    scratch += sprintf(scratch, "SEQNUM=%ld", seq) + 1;

-    kobj_path = kobject_get_path(kset, kobj, GFP_KERNEL);
-    if (!kobj_path)
-        goto exit;
-
    envp [i++] = scratch;
    scratch += sprintf (scratch, "DEVPATH=%s", kobj_path) + 1;

@@ -199,6 +199,13 @@ static void kset_hotplug(const char *act
        if (retval) {
            pr_debug ("%s - hotplug() returned %d\n",
                  __FUNCTION__, retval);
+            /* decr sequence_num since no event will happen
+               but only if it is consistent */
+            spin_lock(&sequence_lock);
+            if (sequence_num == seq+1)
+               sequence_num--;
+            spin_unlock(&sequence_lock);
+
            goto exit;
        }
    }




             reply	other threads:[~2004-10-17  3:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-17  3:47 Andrew [this message]
2004-10-17  8:20 ` [PATCH] kernel-2.6.9.rc4 lib/kobject.c Olaf Hering
2004-10-17 17:14 ` Greg KH

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=4171EB60.50800@speakeasy.net \
    --to=cmkrnl@speakeasy.net \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.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