From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 172E6C433EF for ; Mon, 18 Jul 2022 19:16:13 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=Qn90OkLYYuZBwZgRtOkU1etTJg7jklH7CeyQVFHWriE=; b=3m/FNJznPdjduD vaOki2XutIffPICy2M0pXaJlOJ6jWF8L0V6yhYl2dtcN4e04DbVVkc2EMUeQbSJgGhtR8//TUX/Zq mxmAgzKgORsGhUddwjOOP076Dx5gr23HRJmgxZiaI7z4nab28fIeQ8uURanA1mQrwR24IadGk9C+v YeiYjQKTQ7K/haHaKUEnjfu6kPny3KwulzltcgbL050Y4U6V4fehrfY6XY6iEIDQhEfAmfVrSqJHK trlRHFK9kh7Bu+rG9W++LeBEYCuPLBN/ST802sLS46ukVxAPXdyXxY6syFOrZP3fs40J06Arz5CJ0 fmf/XbGm8AM7MtpO1j7w==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1oDWD7-000Imy-1K; Mon, 18 Jul 2022 19:15:17 +0000 Received: from pandora.armlinux.org.uk ([2001:4d48:ad52:32c8:5054:ff:fe00:142]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1oDWD3-000Ikk-Ic; Mon, 18 Jul 2022 19:15:15 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=armlinux.org.uk; s=pandora-2019; h=Sender:In-Reply-To:Content-Type: MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=G1YSdmImKh2l18ecQ7FfzX2zqvO0awAs2ffUiZkZuSw=; b=uTS4R1PCUCCnZ83svGKLX53ve1 C/11IYua0pNPYugrPmbYoaikCsT12yW4BX/nS2o/OIcmkTQ7YLxqjvT6DLGa7hcqDYn1CIa+6TM6V 7AsENwcdlfZnZ4c1RnhUoU2FfYom1Hqbu1cr4JDB+3UAx7XXI0FS/tX8+wBd5t2wHGqW3jfEgRVgI 7nSahUr1d3h85yXh39YKLE5eLCPi9vcmNFpG5bw805uyFH/yx+Xl1BMFHNl6AQGMiOhzgZ9kDxlhJ oZP0mArmGJuCwOsFPAa+F8EMGsEd/RKGb3+2bvQLeMiMg1HmhDsdOzsdhQok/+fEzmkU/ZBRvIYWF 2kEnXPCA==; Received: from shell.armlinux.org.uk ([fd8f:7570:feb6:1:5054:ff:fe00:4ec]:33434) by pandora.armlinux.org.uk with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1oDWCq-000232-Ra; Mon, 18 Jul 2022 20:15:00 +0100 Received: from linux by shell.armlinux.org.uk with local (Exim 4.94.2) (envelope-from ) id 1oDWCo-0002DB-Tm; Mon, 18 Jul 2022 20:14:58 +0100 Date: Mon, 18 Jul 2022 20:14:58 +0100 From: "Russell King (Oracle)" To: Andy Shevchenko Cc: Vladimir Oltean , Andrew Lunn , Heiner Kallweit , Alexandre Belloni , Alvin __ipraga , Claudiu Manoil , Daniel Scally , "David S. Miller" , DENG Qingfang , Eric Dumazet , Florian Fainelli , George McCollister , Greg Kroah-Hartman , Hauke Mehrtens , Heikki Krogerus , Jakub Kicinski , Kurt Kanzenbach , Landen Chao , Linus Walleij , linux-acpi@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-mediatek@lists.infradead.org, Matthias Brugger , netdev@vger.kernel.org, Paolo Abeni , "Rafael J. Wysocki" , Sakari Ailus , Sean Wang , UNGLinuxDriver@microchip.com, Vivien Didelot , Woojung Huh , Marek =?iso-8859-1?Q?Beh=FAn?= Subject: Re: [PATCH net-next 2/6] software node: allow named software node to be created Message-ID: References: <20220715201715.foea4rifegmnti46@skbuf> <20220715204841.pwhvnue2atrkc2fx@skbuf> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220718_121513_636702_A9B59657 X-CRM114-Status: GOOD ( 40.83 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Mon, Jul 18, 2022 at 09:53:39PM +0300, Andy Shevchenko wrote: > On Mon, Jul 18, 2022 at 09:43:42PM +0300, Andy Shevchenko wrote: > > On Mon, Jul 18, 2022 at 02:27:02PM +0100, Russell King (Oracle) wrote: > > > On Mon, Jul 18, 2022 at 03:29:52PM +0300, Andy Shevchenko wrote: > > > > On Fri, Jul 15, 2022 at 11:48:41PM +0300, Vladimir Oltean wrote: > > > > > So won't kobject_init_and_add() fail on namespace collision? Is it the > > > > > problem that it's going to fail, or that it's not trivial to statically > > > > > determine whether it'll fail? > > > > > > > > > > Sorry, but I don't see something actionable about this. > > > > > > > > I'm talking about validation before a runtime. But if you think that is fine, > > > > let's fail it at runtime, okay, and consume more backtraces in the future. > > > > > > Is there any sane way to do validation of this namespace before > > > runtime? > > > > For statically compiled, I think we can do it (to some extent). > > Currently only three drivers, if I'm not mistaken, define software nodes with > > names. It's easy to check that their node names are unique. > > > > When you allow such an API then we might have tracebacks (from sysfs) bout name > > collisions. Not that is something new to kernel (we have seen many of a kind), > > but I prefer, if possible, to validate this before sysfs issues a traceback. > > > > > The problem in this instance is we need a node named "fixed-link" that > > > is attached to the parent node as that is defined in the binding doc, > > > and we're creating swnodes to provide software generated nodes for > > > this binding. > > > > And how you guarantee that it will be only a single one with unique pathname? > > > > For example, you have two DSA cards (or whatever it's called) in the SMP system, > > it mean that there is non-zero probability of coexisting swnodes for them. > > > > > There could be several such nodes scattered around, but in this > > > instance they are very short-lived before they are destroyed, they > > > don't even need to be published to userspace (and its probably a waste > > > of CPU cycles for them to be published there.) > > > > > > So, for this specific case, is this the best approach, or is there > > > some better way to achieve what we need here? > > > > Honestly, I don't know. > > > > The "workaround" (but it looks to me rather a hack) is to create unique swnode > > and make fixed-link as a child of it. > > > > Or entire concept of the root swnodes (when name is provided) should be > > reconsidered, so somehow we will have a uniqueness so that the entire > > path(s) behind it will be caller-dependent. But this I also don't like. > > > > Maybe Heikki, Sakari, Rafael can share their thoughts... > > > > Just for my learning, why PHY uses "fixed-link" instead of relying on a > > (firmware) graph? It might be the actual solution to your problem. > > > > How graphs are used with swnodes, you may look into IPU3 (Intel Camera) > > glue driver to support devices before MIPI standardisation of the > > respective properties. > > Forgot to say (yes, it maybe obvious) that this API will be exported, > anyone can use it and trap into the similar issue, because, for example, > of testing in environment with a single instance of the caller. I think we're coming to the conclusion that using swnodes is not the correct approach for this problem, correct? -- RMK's Patch system: https://www.armlinux.org.uk/developer/patches/ FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last! _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel