linux-kernel - Re: [PATCH] hwmon/abituguru: handle sysfs errors

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200610120031.20097.dtor@insightbb.com>
Date:	Thu, 12 Oct 2006 00:31:17 -0400
From:	Dmitry Torokhov <dtor@...ightbb.com>
To:	Jean Delvare <khali@...ux-fr.org>
Cc:	Hans de Goede <j.w.r.degoede@....nl>,
	Jeff Garzik <jeff@...zik.org>, Andrew Morton <akpm@...l.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] hwmon/abituguru: handle sysfs errors

On Tuesday 10 October 2006 05:34, Jean Delvare wrote:
> Hans,
> 
> > > * We want to delete all the device files at regular cleanup time (after
> > >   unregistering with the hwmon class).
> > 
> > Is this really nescesarry? AFAIK the files get deleted when the device
> > gets deleted.
> 
> The point is that the device shouldn't be deleted if we were following
> the device driver model. After all the uGuru device exists in your
> system before the abituguru driver is loaded, and is still there after
> the driver is unloaded.
> 
> Now I agree that for now it won't make a difference, be we are
> preparing for the future, and all other hardware monitoring drivers
> were updated that way already.
> 
> > > * It's OK to call device_create_file() on a non-existent file, so the
> > >   error path can be simplified.
> > 
> > ?? You mean device_remove_file I assume?
> 
> Oops, yes, that was a typo, sorry.
> 

I know I sound like a roken record but this driver would benefit from
using attribute_group.

-- 
Dmitry
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/