Received: by 2002:a05:6359:c8b:b0:c7:702f:21d4 with SMTP id go11csp3118512rwb; Mon, 3 Oct 2022 09:55:45 -0700 (PDT) X-Google-Smtp-Source: AMsMyM7swZJu6Km8ZlFRRlkHa5faNvQcCpk9TAhBoDTM4EJkzey3A67mgg3bc99nLqGhDnrkXZl3 X-Received: by 2002:a05:6402:22ed:b0:458:bcd1:69cf with SMTP id dn13-20020a05640222ed00b00458bcd169cfmr9992754edb.260.1664816145436; Mon, 03 Oct 2022 09:55:45 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1664816145; cv=none; d=google.com; s=arc-20160816; b=XIVfbx7sIpU91exseI81PH/D+i/J7XW6i1iWrSkw0zokQfXW6B+L9YOAPntcwr2FDZ /iLvmY9cOvOivtJNBNP4kUcwi6aGf2UsFNyTZn8ci7/xFSBvK1rrKWGR5xBweYIMrpQb qoUHlsDVM7P2/MEcmAt1KkRPlAqQ0sEKSQHWCEMi+mSSVfLrrR6fIA9XTkQA+ssj54Mk bhNoYYAaAbt5NEQwHYP5KLrmyCEKqc9eONq9Gcz1+Tu3k2Qmqih+qMaMc/bEa1Qb3zbK 3V14lnLayg+0prZKn9q7iobz4+ZJUMEje4U89MYxNR98sFpK10IqS+EFoKcXnKvxvRXL JyLw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-transfer-encoding :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=rg+Ot+OC/KajvXN3aL2RNmUbl3fowMO+HNQLnEqxM9Q=; b=RE16XFAH7mhk5A9lvV9swBfjyJnZpLIdMAZMMFFxEeCI+hqutHYD2VbWn3D7+SziL5 TISQVy2J5CVhacz+QuqHIlJZ8UO2Td2++sBcQGqCH9sRh3jJ/iN++i1hlb0WNK1HvwmP gaNgCXtf1xNnDT8JfFp1xRZSGQiOmwP33/Z0bjeHnlqCnDQmJGJHmOqOIy/98xZZss1g fAWQPdZLpEB39572SYFsDxI7av44tpa5CnpyA/aUpiBxtdh5rwNRAzWFPFQpheWuZfBn 8qDhpIpO6KLgCPCeetRU3/MGNT9Dz+93/7DwQJ4QCBfHa3h/G87SNCGp3isl0bvAqCUU U3zg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=WoQWJ5Uz; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id hv16-20020a17090760d000b007708400bee0si8651355ejc.620.2022.10.03.09.55.19; Mon, 03 Oct 2022 09:55:45 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=WoQWJ5Uz; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229774AbiJCQRd (ORCPT + 99 others); Mon, 3 Oct 2022 12:17:33 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35240 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229775AbiJCQRZ (ORCPT ); Mon, 3 Oct 2022 12:17:25 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id F0CB233E1C; Mon, 3 Oct 2022 09:17:21 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 8CB696112D; Mon, 3 Oct 2022 16:17:21 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 66BF8C433D6; Mon, 3 Oct 2022 16:17:20 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1664813840; bh=s96hTsxFQJxWDg9Af3wR2mq5yoGoEwVzUCGwHfgUdF0=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=WoQWJ5UzYX1l9KUoj7lhjj/rI5K8zj8XaRUubxsvH2v/8l/+dxUfogI970NeNG58h wU6kFDMtTLL9JyR11zVUWj6/9DAnz8XH1/fEr/zBrwmu4JInvWbjWQDxuuTYUPnd1O CeOwJI9GfU5CllOVPKETnJRKK+x5tFPwXdOPkD/w= Date: Mon, 3 Oct 2022 18:17:17 +0200 From: Greg Kroah-Hartman To: Sakari Ailus Cc: Andy Shevchenko , Heikki Krogerus , Bjorn Andersson , Prashant Malani , linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org, Daniel Scally , "Rafael J. Wysocki" Subject: Re: [PATCH v2 1/5] device property: Keep dev_fwnode() and dev_fwnode_const() separate Message-ID: References: <20220928105746.51208-1-andriy.shevchenko@linux.intel.com> <20220928105746.51208-2-andriy.shevchenko@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Spam-Status: No, score=-7.1 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Oct 03, 2022 at 05:07:27PM +0200, Greg Kroah-Hartman wrote: > On Mon, Oct 03, 2022 at 11:02:19AM +0000, Sakari Ailus wrote: > > Hi Greg, > > > > On Fri, Sep 30, 2022 at 04:43:19PM +0200, Greg Kroah-Hartman wrote: > > > On Fri, Sep 30, 2022 at 02:30:53PM +0000, Sakari Ailus wrote: > > > > Hi Greg, > > > > > > > > On Wed, Sep 28, 2022 at 01:05:20PM +0200, Greg Kroah-Hartman wrote: > > > > > On Wed, Sep 28, 2022 at 01:57:42PM +0300, Andy Shevchenko wrote: > > > > > > It's not fully correct to take a const parameter pointer to a struct > > > > > > and return a non-const pointer to a member of that struct. > > > > > > > > > > > > Instead, introduce a const version of the dev_fwnode() API which takes > > > > > > and returns const pointers and use it where it's applicable. > > > > > > > > > > > > Suggested-by: Sakari Ailus > > > > > > Fixes: aade55c86033 ("device property: Add const qualifier to device_get_match_data() parameter") > > > > > > Signed-off-by: Andy Shevchenko > > > > > > Acked-by: Heikki Krogerus > > > > > > Reviewed-by: Sakari Ailus > > > > > > --- > > > > > > drivers/base/property.c | 11 +++++++++-- > > > > > > include/linux/property.h | 3 ++- > > > > > > 2 files changed, 11 insertions(+), 3 deletions(-) > > > > > > > > > > > > diff --git a/drivers/base/property.c b/drivers/base/property.c > > > > > > index 4d6278a84868..699f1b115e0a 100644 > > > > > > --- a/drivers/base/property.c > > > > > > +++ b/drivers/base/property.c > > > > > > @@ -17,13 +17,20 @@ > > > > > > #include > > > > > > #include > > > > > > > > > > > > -struct fwnode_handle *dev_fwnode(const struct device *dev) > > > > > > +struct fwnode_handle *dev_fwnode(struct device *dev) > > > > > > { > > > > > > return IS_ENABLED(CONFIG_OF) && dev->of_node ? > > > > > > of_fwnode_handle(dev->of_node) : dev->fwnode; > > > > > > } > > > > > > EXPORT_SYMBOL_GPL(dev_fwnode); > > > > > > > > > > > > +const struct fwnode_handle *dev_fwnode_const(const struct device *dev) > > > > > > +{ > > > > > > + return IS_ENABLED(CONFIG_OF) && dev->of_node ? > > > > > > + of_fwnode_handle(dev->of_node) : dev->fwnode; > > > > > > +} > > > > > > +EXPORT_SYMBOL_GPL(dev_fwnode_const); > > > > > > > > > > Ick, no, this is a mess. > > > > > > > > > > Either always return a const pointer, or don't. Ideally always return a > > > > > const pointer, so all we really need is: > > > > > > > > > > const struct fwnode_handle *dev_fwnode(const struct device *dev); > > > > > > > > > > right? > > > > > > > > > > Yes, it will take some unwinding backwards to get there, but please do > > > > > that instead of having 2 different functions where the parameter type is > > > > > part of the function name. This isn't the 1980's... > > > > > > > > The problem with this approach is that sometimes non-const fwnode_handles > > > > are needed. On OF, for instance, anything that has something to do with > > > > refcounting requires this. Software nodes as well. > > > > > > If they are writable, then yes, let's keep them writable, and not create > > > two function paths where we have to pick and choose. > > > > > > > One option which I suggested earlier was to turn dev_fwnode() into a macro > > > > and use C11 _Generic() to check whether the device is const or not. > > > > > > As much fun as that would be, I don't think it would work well. > > > > > > Although, maybe it would, have an example of how that would look? > > > > Similar to what container_of() could be, see below. > > > > We could also partially revert aade55c86033bee868a93e4bf3843c9c99e84526 > > which (also) made dev_fwnode() argument const (which is the source of the > > issue). > > > > > > > > I ask as I just went through a large refactoring of the kobject layer to > > > mark many things const * and I find it a bit "sad" that functions like > > > this: > > > static inline struct device *kobj_to_dev(const struct kobject *kobj) > > > { > > > return container_of(kobj, struct device, kobj); > > > } > > > have the ability to take a read-only pointer and spit out a writable one > > > thanks to the pointer math in container_of() with no one being the > > > wiser. > > > > Yeah, container_of() is dangerous, especially in macros. It could of course > > be made safer. Something like this: > > > > > > > > I can respin it, back in 2017 I got no replies. > > I don't like how we loose the ability to do this in an inline C function > by being forced to do it in a macro (as it makes build errors harder to > understand), but I do like the intent here. > > Let me play around with this a bit on some "smaller" uses of > container_of() and see how that works... Odd, this doesn't work for me at all. I tried the following change: diff --git a/include/linux/device.h b/include/linux/device.h index 424b55df0272..5575c87e6c3b 100644 --- a/include/linux/device.h +++ b/include/linux/device.h @@ -680,11 +680,21 @@ struct device_link { bool supplier_preactivated; /* Owned by consumer probe. */ }; -static inline struct device *kobj_to_dev(struct kobject *kobj) +static inline struct device *__kobj_to_dev(struct kobject *kobj) { return container_of(kobj, struct device, kobj); } +static inline const struct device *__kobj_to_dev_const(const struct kobject *kobj) +{ + return container_of(kobj, const struct device, kobj); +} + +#define kobj_to_dev(kobj) \ + _Generic((kobj), \ + const struct kobject *: __kobj_to_dev_const(kobj), \ + struct kobject *: __kobj_to_dev(kobj)) + /** * device_iommu_mapped - Returns true when the device DMA is translated * by an IOMMU which seems all is fine for normal kobject pointers passed in, but for the first 'const struct kobject *' the compiler hits, I get the following error: CC drivers/base/core.o In file included from ./include/linux/acpi.h:15, from drivers/base/core.c:11: drivers/base/core.c: In function ‘dev_attr_show’: drivers/base/core.c:2193:48: error: passing argument 1 of ‘__kobj_to_dev’ discards ‘const’ qualifier from pointer target type [-Werror=discarded-qualifiers] 2193 | const struct device *dev = kobj_to_dev(kobj); | ^~~~ ./include/linux/device.h:696:50: note: in definition of macro ‘kobj_to_dev’ 696 | struct kobject *: __kobj_to_dev(kobj)) | ^~~~ ./include/linux/device.h:683:60: note: expected ‘struct kobject *’ but argument is of type ‘const struct kobject *’ 683 | static inline struct device *__kobj_to_dev(struct kobject *kobj) | ~~~~~~~~~~~~~~~~^~~~ (note, I faked up a constant pointer just to trip the compiler) The selection of _Generic() seems not to be working here, any hints? I tried playing around with 'default' and 'typeof' and the like, but all error out the same way. thanks, greg k-h