From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: libsysfs/udev hang
Date: Tue, 23 Mar 2004 15:57:56 +0000 [thread overview]
Message-ID: <20040323155756.GA30122@kroah.com> (raw)
In-Reply-To: <4060259D.4000905@gmx.net>
On Tue, Mar 23, 2004 at 12:55:09PM +0100, Carl-Daniel Hailfinger wrote:
> sysfs_dev = sysfs_get_classdev_device(class_dev);
> if (sysfs_dev != NULL)
> printf("follow the class device's \"device\"\n");
>
> /* look the device chain upwards */
> while (sysfs_dev != NULL) {
<snip>
> sysfs_dev_parent = sysfs_get_device_parent(sysfs_dev);
> printf("point4\n");
> if (sysfs_dev_parent = NULL)
> break;
> printf("point5\n");
>
> sysfs_dev = sysfs_dev_parent;
> printf("point6\n");
> }
> printf("point7\n");
> sysfs_close_device(sysfs_dev);
At this point in time, sysfs_dev will not point to the oritinal device
you got from the sysfs_get_glassdev_device() call, right?
That's probably the bug.
Hope this helps,
greg k-h
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id\x1470&alloc_id638&op=click
_______________________________________________
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:[~2004-03-23 15:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-23 11:55 libsysfs/udev hang Carl-Daniel Hailfinger
2004-03-23 15:57 ` Greg KH [this message]
2004-03-23 17:04 ` Carl-Daniel Hailfinger
2004-03-23 19:09 ` Greg KH
2004-03-23 19:19 ` Daniel Stekloff
2004-03-23 19:24 ` Daniel Stekloff
2004-03-23 20:57 ` Carl-Daniel Hailfinger
2004-03-24 1: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=20040323155756.GA30122@kroah.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.