From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752135AbWJZJTo (ORCPT ); Thu, 26 Oct 2006 05:19:44 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752134AbWJZJTo (ORCPT ); Thu, 26 Oct 2006 05:19:44 -0400 Received: from gate.crashing.org ([63.228.1.57]:19120 "EHLO gate.crashing.org") by vger.kernel.org with ESMTP id S1752135AbWJZJTn (ORCPT ); Thu, 26 Oct 2006 05:19:43 -0400 Subject: Re: [Cbe-oss-dev] [PATCH 12/16] cell: add temperature to SPU and CPU sysfs entries From: Benjamin Herrenschmidt To: Arnd Bergmann Cc: Heiko Carstens , linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org, cbe-oss-dev@ozlabs.org, Andrew Morton In-Reply-To: <200610260935.01801.arnd@arndb.de> References: <20061024163113.694643000@arndb.de> <20061025080048.GB7090@osiris.boeblingen.de.ibm.com> <1161818364.22582.145.camel@localhost.localdomain> <200610260935.01801.arnd@arndb.de> Content-Type: text/plain Date: Thu, 26 Oct 2006 19:19:02 +1000 Message-Id: <1161854342.5299.30.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.8.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 2006-10-26 at 09:35 +0200, Arnd Bergmann wrote: > On Thursday 26 October 2006 01:19, Benjamin Herrenschmidt wrote: > > > > > > Will crash if cpu_add_sysdev_attr_group failed... > > > > > > Which is a total PITA. If this is the case, then we should modify the > > add calls to at least initialize enough fields before they can fail for > > the remove calls not to crash. You don't want to keep track precisely of > > what file was added and what not and test all of that in your exit code > > path, it's just insane. > > Heiko suggested that earlied in http://lkml.org/lkml/2006/10/9/22, > but Andrew didn't like it. > > Currently, the worst is that sysfs_remove_file can be used > on a nonexisting file, but sysfs_remove_group cannot, which is > inconsistent. Either sysfs_remove_file should WARN_ON or > sysfs_remove_group should silently return, and I'd prefer the > latter, as it makes users simpler. We need to argue with Andrew then. I'll have a go tomorrow Ben.