linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2004@gmx.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: libsysfs/udev hang
Date: Tue, 23 Mar 2004 17:04:16 +0000	[thread overview]
Message-ID: <40606E10.8030800@gmx.net> (raw)
In-Reply-To: <4060259D.4000905@gmx.net>

Greg KH wrote:
> 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?

Right.

> That's probably the bug.

Then it has to be fixed in udevinfo.c:print_device_chain, too.

Unfortunately this does not explain why the lockup vanishes once I compile
with DEBUG=true. Added debugging should not change the behaviour of a
library, right?


Thanks,
Carl-Daniel



-------------------------------------------------------
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

  parent reply	other threads:[~2004-03-23 17:04 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
2004-03-23 17:04 ` Carl-Daniel Hailfinger [this message]
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=40606E10.8030800@gmx.net \
    --to=c-d.hailfinger.kernel.2004@gmx.net \
    --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).