From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [ANNOUNCE] udev 004 release
Date: Wed, 22 Oct 2003 01:46:39 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-106684257524239@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-106675444401980@msgid-missing>
On Tue, Oct 21, 2003 at 03:13:38PM -0700, Greg KH wrote:
> On Tue, Oct 21, 2003 at 02:45:55PM -0700, Jesse Barnes wrote:
> > Thanks for the new release, Greg. I just tried it out on a system with
> > some disks, but a bunch of udev processes ended up hanging. Is there
> > something I'm missing or do you need a patch like this?
>
> Yeah, sorry, this kind of fix is required :(
>
> It's fixed in my bk tree now.
>
> Oh, and it looks like the LABEL rule is also broken due to the libsysfs
> changes... I'm working on adding regression tests right now to prevent
> things like this from slipping through.
Here's a patch for this. It fixes the problem of LABEL rules on the
device, not the class device. LABEL rules on the class device seem to
work just fine.
Thanks to Dan Stekloff for help in finding this bug.
thanks,
greg k-h
# fix LABEL bug for device files (not class files.)
diff -Nru a/namedev.c b/namedev.c
--- a/namedev.c Tue Oct 21 18:44:59 2003
+++ b/namedev.c Tue Oct 21 18:44:59 2003
@@ -566,7 +566,7 @@
/* look in the class device directory if present */
if (class_dev->sysdevice) {
- tmpattr = sysfs_get_classdev_attr(class_dev, dev->sysfs_file);
+ tmpattr = sysfs_get_device_attr(class_dev->sysdevice, dev->sysfs_file);
if (tmpattr)
goto label_found;
}
@@ -599,7 +599,7 @@
/* look in the class device directory if present */
if (class_dev_parent->sysdevice) {
- tmpattr = sysfs_get_classdev_attr(class_dev_parent, dev->sysfs_file);
+ tmpattr = sysfs_get_device_attr(class_dev_parent->sysdevice, dev->sysfs_file);
if (tmpattr)
goto label_found;
}
-------------------------------------------------------
This SF.net email is sponsored by OSDN developer relations
Here's your chance to show off your extensive product knowledge
We want to know what you know. Tell us and you have a chance to win $100
http://www.zoomerang.com/survey.zgi?HRPT1X3RYQNC5V4MLNSV3E54
_______________________________________________
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
next prev parent reply other threads:[~2003-10-22 1:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-21 16:28 [ANNOUNCE] udev 004 release Greg KH
2003-10-21 20:34 ` Kay Sievers
2003-10-21 20:50 ` Greg KH
2003-10-21 21:45 ` Jesse Barnes
2003-10-21 22:13 ` Greg KH
2003-10-22 1:46 ` Greg KH [this message]
2003-10-22 3:24 ` Kay Sievers
2003-10-22 7:09 ` Daniel Stekloff
2003-10-22 8:52 ` Ananth N Mavinakayanahalli
2003-10-22 23:52 ` Greg KH
2003-10-24 13:42 ` Kay Sievers
2003-10-25 10:40 ` Erik van Konijnenburg
2003-10-25 10:40 ` Erik van Konijnenburg
2003-11-14 1:36 ` Greg KH
2003-11-23 21:32 ` 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=marc-linux-hotplug-106684257524239@msgid-missing \
--to=greg@kroah.com \
--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;
as well as URLs for NNTP newsgroup(s).