From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andi Kleen Subject: Re: linux-next: Tree for August 14 (sysfs/acpi errors) Date: Sun, 17 Aug 2008 05:53:07 +0200 Message-ID: <87hc9kxpp8.fsf@basil.nowhere.org> References: <20080814172945.250a27f2.sfr@canb.auug.org.au> <20080814083828.d10e126d.randy.dunlap@oracle.com> <3ae72650808150427q364842ccicf0a0978b30ca98c@mail.gmail.com> <20080815085836.67e420f1.randy.dunlap@oracle.com> <1218854219.3629.30.camel@lgn.site> <48A64235.2030108@linux.intel.com> <1218856798.3629.45.camel@lgn.site> <48A64E0A.8090408@linux.intel.com> <20080816044714.GA19886@kroah.com> <48A78D4A.70609@linux.intel.com> <20080817034051.GA26849@kroah.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: In-Reply-To: <20080817034051.GA26849@kroah.com> (Greg KH's message of "Sat, 16 Aug 2008 20:40:51 -0700") Sender: linux-acpi-owner@vger.kernel.org To: Greg KH Cc: Kay Sievers , Randy Dunlap , Stephen Rothwell , linux-next@vger.kernel.org, LKML , linux-acpi@vger.kernel.org, rusty@rustcorp.com.au List-Id: linux-next.vger.kernel.org Greg KH writes: >> No! > > What you are doing here is wrong, trying to create two files with the > same name. You just should not be doing that at all, it's that simple. > Fix the broken code/link order, don't paper it over in the sysfs layer. Sorry, but relying on link order for anything is a mistake. It is subtle and fragile and just means it'll eventually break again because it's near impossible to properly maintain. The alternative is to always check if the file exists in the params.c code before creating it. We can do that too, but it's somewhat dumb because sysfs is already doing that. -Andi