From: Jean Delvare <khali@linux-fr.org>
To: Hans de Goede <j.w.r.degoede@hhs.nl>
Cc: Jeff Garzik <jeff@garzik.org>, Andrew Morton <akpm@osdl.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] hwmon/abituguru: handle sysfs errors
Date: Tue, 10 Oct 2006 11:08:03 +0200 [thread overview]
Message-ID: <20061010110803.1a70b576.khali@linux-fr.org> (raw)
In-Reply-To: <452B4B59.1050606@hhs.nl>
Hi Hans, Jeff,
> You (Jean) already mailed me about this and it was on my todo list,
> but I'm currently rather busy with work. So it looks like Jeff beat
> me to it.
>
> Jeff's patch looks fine, please apply. Thanks Jeff!
The patch isn't wrong per se, but it could be made more simple, and is
incomplete in comparison to what was done for all other hardware
monitoring drivers:
* We want to create all the files before registering with the hwmon
class, this closes a race condition.
* We want to delete all the device files at regular cleanup time (after
unregistering with the hwmon class).
* It's OK to call device_create_file() on a non-existent file, so the
error path can be simplified.
I'd like the abituguru driver to behave the same as all other hardware
monitoring drivers to lower the maintenance effort. Can either you
or Jeff work up a compliant patch?
Thanks.
> drivers/hwmon/abituguru.c | 30 +++++++++++++++++++++++++-----
> 1 file changed, 25 insertions(+), 5 deletions(-)
>
> 2b10f648c8ed965369976eb7925b922ee187ce21
> diff --git a/drivers/hwmon/abituguru.c b/drivers/hwmon/abituguru.c
> index e5cb0fd..3ded982 100644
> --- a/drivers/hwmon/abituguru.c
> +++ b/drivers/hwmon/abituguru.c
> @@ -1271,14 +1271,34 @@ static int __devinit abituguru_probe(str
> res = PTR_ERR(data->class_dev);
> goto abituguru_probe_error;
> }
> - for (i = 0; i < sysfs_attr_i; i++)
> - device_create_file(&pdev->dev, &data->sysfs_attr[i].dev_attr);
> - for (i = 0; i < ARRAY_SIZE(abituguru_sysfs_attr); i++)
> - device_create_file(&pdev->dev,
> - &abituguru_sysfs_attr[i].dev_attr);
> + for (i = 0; i < sysfs_attr_i; i++) {
> + res = device_create_file(&pdev->dev,
> + &data->sysfs_attr[i].dev_attr);
> + if (res) {
> + for (j = 0; j < i; j++)
> + device_remove_file(&pdev->dev,
> + &data->sysfs_attr[j].dev_attr);
> + goto err_devreg;
> + }
> + }
> + for (i = 0; i < ARRAY_SIZE(abituguru_sysfs_attr); i++) {
> + res = device_create_file(&pdev->dev,
> + &abituguru_sysfs_attr[i].dev_attr);
> + if (res) {
> + for (j = 0; j < i; j++)
> + device_remove_file(&pdev->dev,
> + &abituguru_sysfs_attr[j].dev_attr);
> + goto err_attr_i;
> + }
> + }
>
> return 0;
>
> +err_attr_i:
> + for (i = 0; i < sysfs_attr_i; i++)
> + device_remove_file(&pdev->dev, &data->sysfs_attr[i].dev_attr);
> +err_devreg:
> + hwmon_device_unregister(data->class_dev);
> abituguru_probe_error:
> kfree(data);
> return res;
--
Jean Delvare
next prev parent reply other threads:[~2006-10-10 9:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-10 6:53 [PATCH] hwmon/abituguru: handle sysfs errors Jeff Garzik
2006-10-10 7:27 ` Hans de Goede
2006-10-10 9:08 ` Jean Delvare [this message]
2006-10-10 9:18 ` Hans de Goede
2006-10-10 9:34 ` Jean Delvare
2006-10-12 4:31 ` Dmitry Torokhov
2006-10-12 15:42 ` Jean Delvare
2006-10-16 3:56 ` Dmitry Torokhov
2006-12-02 11:36 ` Jean Delvare
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=20061010110803.1a70b576.khali@linux-fr.org \
--to=khali@linux-fr.org \
--cc=akpm@osdl.org \
--cc=j.w.r.degoede@hhs.nl \
--cc=jeff@garzik.org \
--cc=linux-kernel@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