From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: swich attribute open() to simple stat()
Date: Fri, 15 Oct 2004 20:55:21 +0000 [thread overview]
Message-ID: <20041015205521.GA16561@kroah.com> (raw)
In-Reply-To: <20041015173619.GD6056@vrfy.org>
On Fri, Oct 15, 2004 at 07:36:19PM +0200, Kay Sievers wrote:
> Here we switch to a simple stat() to recognize the file creation. This
> will make it possible to wait for files, which are unreadable.
>
> I've switched the timout back to 5 seconds cause the our /class/vc errors
> seems like a bug in the vc layer not a sysfs delay.
>
> Thanks,
> Kay
> === wait_for_sysfs.c 1.18 vs edited ==> --- 1.18/wait_for_sysfs.c 2004-10-14 16:14:00 +02:00
> +++ edited/wait_for_sysfs.c 2004-10-15 19:32:38 +02:00
> @@ -47,7 +47,7 @@ void log_message(int level, const char *
> }
> #endif
>
> -#define WAIT_MAX_SECONDS 10
> +#define WAIT_MAX_SECONDS 5
> #define WAIT_LOOP_PER_SECOND 20
>
> /* wait for specific file to show up, normally the "dev"-file */
> @@ -60,7 +60,7 @@ static int wait_for_class_device_attribu
> { .subsystem = "net", .file = "ifindex" },
> { .subsystem = "scsi_host", .file = "unique_id" },
> { .subsystem = "scsi_device", .file = NULL },
> - { .subsystem = "pcmcia_socket", .file = NULL }, /* all files are unreadable in empty slot :( */
> + { .subsystem = "pcmcia_socket", .file = "card_type" },
> { .subsystem = "usb_host", .file = NULL },
> { .subsystem = "bluetooth", .file = "address" },
> { .subsystem = "firmware", .file = "data" },
> @@ -86,11 +86,14 @@ static int wait_for_class_device_attribu
> break;
> }
> }
> - dbg("looking at class '%s' for specific file '%s'", class_dev->classname, file);
> +
> + dbg("looking at class '%s' for specific file '%s'", class_dev->classname, class_dev->path);
>
> loop = WAIT_MAX_SECONDS * WAIT_LOOP_PER_SECOND;
> while (--loop) {
> - if (sysfs_get_classdev_attr(class_dev, file) != NULL) {
> + struct stat stats;
> +
> + if (stat(class_dev->path, &stats) = 0) {
Wait, this patch stops us from looking for "file" which had been set to
the file we wanted to look at, right? Now we are just verifying that
the sysfs _directory_ for the class device is present.
While this is a good check (and we should do this to verify that the
device hasn't gone away, like in the vcs issue), I don't think this is
what you wanted to do, right?
thanks,
greg k-h
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
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-10-15 20:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-15 17:36 swich attribute open() to simple stat() Kay Sievers
2004-10-15 18:48 ` Greg KH
2004-10-15 20:55 ` Greg KH [this message]
2004-10-15 21:58 ` Greg KH
2004-10-15 22:38 ` 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=20041015205521.GA16561@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 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).