public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 0/2] fs: sysfs: Add devres support
Date: Sat, 16 Mar 2013 09:21:40 -0700	[thread overview]
Message-ID: <20130316162140.GB2630@kroah.com> (raw)
In-Reply-To: <1363317887-24009-1-git-send-email-linux@roeck-us.net>

On Thu, Mar 14, 2013 at 08:24:45PM -0700, Guenter Roeck wrote:
> Provide devres functions for device_create_file, sysfs_create_file,
> and sysfs_create_group plus the respective remove functions.
> 
> Idea is to be able to drop calls to the remove functions from the various
> drivers using those calls.

Hm, despite the fact that almost every driver that makes these calls is
broken?  :)

> Potential savings are substantial. There are more than 700 calls to
> device_remove_file in the kernel, more than 500 calls to sysfs_remove_group,
> and some 50 calls to sysfs_remove_file (though not all of those use dev->kobj
> as parameter). Expanding the API to sysfs_create_bin_file would add another 80+
> opportunities, and adding sysfs_create_link would create another 100 or so.

The idea is nice, but why are these drivers adding sysfs files on their
own?  Are they doing this in a way that is race-free with userspace
(i.e. creating them before userspace is told about the device), or are
they broken and need to have these calls added to the "default
device/driver/bus" attribute list for them instead?

I think the "we need to fix the drivers" option is the correct one :(

Ideally, I could get rid of those files from being exported at all, but
some busses do do things correctly, so I can't.  But they seem to be in
the minority...

So how about we fix up the drivers first, then, if there are valid users
for this type of interface (which I do think there is), we can add it
then?

thanks,

greg k-h

  parent reply	other threads:[~2013-03-16 16:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-15  3:24 [RFC PATCH 0/2] fs: sysfs: Add devres support Guenter Roeck
2013-03-15  3:24 ` [RFC PATCH 1/2] fs: sysfs: Add support for devm_ functions Guenter Roeck
2013-03-15  3:24 ` [RFC PATCH 2/2] drivers/core: " Guenter Roeck
2013-03-16 16:21 ` Greg Kroah-Hartman [this message]
2013-03-16 18:12   ` [RFC PATCH 0/2] fs: sysfs: Add devres support Guenter Roeck
2013-03-16 19:50     ` Greg Kroah-Hartman
2013-03-16 21:25       ` Guenter Roeck
2013-03-17  6:30         ` [lm-sensors] " Guenter Roeck
2013-03-17 12:39         ` Jean Delvare
2013-03-17 13:19           ` Guenter Roeck
2013-03-17 14:54             ` Guenter Roeck
2013-03-18  8:02             ` Jean Delvare
2013-03-18 13:29               ` Guenter Roeck
2013-11-22 22:47   ` Dmitry Torokhov
2013-11-22 22:53     ` Greg Kroah-Hartman

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=20130316162140.GB2630@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    /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