From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759043AbbJ3PNr (ORCPT ); Fri, 30 Oct 2015 11:13:47 -0400 Received: from mail-qk0-f173.google.com ([209.85.220.173]:33749 "EHLO mail-qk0-f173.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750834AbbJ3PN0 (ORCPT ); Fri, 30 Oct 2015 11:13:26 -0400 Date: Fri, 30 Oct 2015 08:13:11 -0700 From: Dmitry Torokhov To: Greg Kroah-Hartman Cc: htejun@gmail.com, linux-kernel@vger.kernel.org Subject: Re: [PATCH] sysfs: add devm_sysfs_create_group() and friends Message-ID: <20151030151311.GA20183@dtor-pixel> References: <20151030114706.GA2243@localhost> <20151030144037.GC27072@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20151030144037.GC27072@kroah.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Oct 30, 2015 at 07:40:37AM -0700, Greg Kroah-Hartman wrote: > On Fri, Oct 30, 2015 at 04:47:06AM -0700, Dmitry Torokhov wrote: > > Many drivers create additional driver-specific device attributes when > > binding to the device and providing managed version of sysfs_create_group() > > will simplify unbinding and error handling in probe path for such drivers. > > But they really shouldn't, because if they do this, they have raced > userspace and tools don't know that the files are present. > > I don't want to encourage drivers to do this at all, so I don't want to > make it easier for them to do things incorrectly. The solution is not to forbid drivers from establishing attributes but rather notify userspace when device is fully bound to the driver. Then userspace that actually cares about these attributes will listen to proper events. We can either do KOBJ_BOUND/KOBJ_UNBOUND or reuse KOBJ_ONLINE/KOBJ_OFFLINE. I'd prefer the former (adding new events). > > Yes, I know that input does this for its devices, but I still think it > is wrong and should be changed. Let's not let this problem spread to > other subsystems please. Like HID, chargers, hwmon, wireless drivers, leds, backlights, platform drivers and so on? Where are platform devices supposed to create their attributes? There are more than 300 drivers that add new groups and 581 instance of device_create_file(). Let's be realistic here and see that additional attributes are not going anywhere and adding devm interface just helps getting error handling right. Thanks. -- Dmitry