Linux Hotplug development
 help / color / mirror / Atom feed
From: Pozsar Balazs <pozsy@uhulinux.hu>
To: linux-hotplug@vger.kernel.org
Subject: [PATCH] udevsettle should read udev not kernel seqnum first
Date: Fri, 23 Mar 2007 14:46:56 +0000	[thread overview]
Message-ID: <20070323144655.GD30083@ojjektum.uhulinux.hu> (raw)


Hi all,

I think that the order of reading the kernel and udev seqnum files 
should be: first udev, then kernel, because with the current code 
there's a chance of exiting too early, for example in the following 
scenario:
 1. kernel seqnum is X, udevsettle reads it
 2. udev finishes processing the event X, which generates new events
    (for example a modprobe), udev seqnum becomes X
 3. udevsettle reads the udev seqnum which is X now, so it exits
 4. at least another event comes which should have been waited for

Attached patch changes the order to first read the udev seqnum.


diff -Naurd a/udevsettle.c b/udevsettle.c
--- a/udevsettle.c	2006-04-15 19:32:38.000000000 +0200
+++ b/udevsettle.c	2006-04-25 21:40:57.000000000 +0200
@@ -111,9 +111,9 @@
 			goto exit;
 		}
 
-		/* read current kernel seqnum */
-		strlcpy(filename, sysfs_path, sizeof(filename));
-		strlcat(filename, "/kernel/uevent_seqnum", sizeof(filename));
+		/* read current udev seqnum */
+		strlcpy(filename, udev_root, sizeof(filename));
+		strlcat(filename, "/" EVENT_SEQNUM, sizeof(filename));
 		fd = open(filename, O_RDONLY);
 		if (fd < 0)
 			goto exit;
@@ -122,12 +122,12 @@
 		if (len <= 0)
 			goto exit;
 		seqnum[len] = '\0';
-		seq_kernel = strtoull(seqnum, NULL, 10);
-		info("kernel seqnum = %llu", seq_kernel);
+		seq_udev = strtoull(seqnum, NULL, 10);
+		info("udev seqnum = %llu", seq_udev);
 
-		/* read current udev seqnum */
-		strlcpy(filename, udev_root, sizeof(filename));
-		strlcat(filename, "/" EVENT_SEQNUM, sizeof(filename));
+		/* read current kernel seqnum */
+		strlcpy(filename, sysfs_path, sizeof(filename));
+		strlcat(filename, "/kernel/uevent_seqnum", sizeof(filename));
 		fd = open(filename, O_RDONLY);
 		if (fd < 0)
 			goto exit;
@@ -136,8 +136,8 @@
 		if (len <= 0)
 			goto exit;
 		seqnum[len] = '\0';
-		seq_udev = strtoull(seqnum, NULL, 10);
-		info("udev seqnum = %llu", seq_udev);
+		seq_kernel = strtoull(seqnum, NULL, 10);
+		info("kernel seqnum = %llu", seq_kernel);
 
 		/* make sure all kernel events have arrived in the queue */
 		if (seq_udev >= seq_kernel) {


-- 
pozsy

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CIDÞVDEV
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

             reply	other threads:[~2007-03-23 14:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-23 14:46 Pozsar Balazs [this message]
2007-03-23 16:26 ` [PATCH] udevsettle should read udev not kernel seqnum first Kay Sievers
2007-03-23 16:36 ` Pozsar Balazs
2007-03-23 16:53 ` Kay Sievers

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=20070323144655.GD30083@ojjektum.uhulinux.hu \
    --to=pozsy@uhulinux.hu \
    --cc=linux-hotplug@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