From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Thomas Weißschuh" <linux@weissschuh.net>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/6] sysfs: attribute_group: allow registration of const attribute
Date: Fri, 17 Jan 2025 08:01:00 +0100 [thread overview]
Message-ID: <2025011714-skeleton-bring-3e77@gregkh> (raw)
In-Reply-To: <20250116-sysfs-const-attr-prep-v1-1-15e72dba4205@weissschuh.net>
On Thu, Jan 16, 2025 at 06:32:27PM +0100, Thomas Weißschuh wrote:
> To be able to constify instances of struct attribute it has to be
> possible to add them to struct attribute_group.
> The current type of the attrs member however is not compatible with that.
> Introduce a union that allows registration of both const and non-const
> attributes to enable a piecewise transition.
> As both union member types are compatible no logic needs to be adapted.
>
> Technically it is now possible register a const struct
> attribute and receive it as mutable pointer in the callbacks.
> This is a soundness issue.
> But this same soundness issue already exists today in
> sysfs_create_file().
> Also the struct definition and callback implementation are always
> closely linked and are meant to be moved to const in lockstep.
>
> Similar to commit 906c508afdca ("sysfs: attribute_group: allow registration of const bin_attribute")
>
> Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
> ---
> include/linux/sysfs.h | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/include/linux/sysfs.h b/include/linux/sysfs.h
> index 0f2fcd244523f050c5286f19d4fe1846506f9214..f5e25bed777a6a6e717f10973f1abcd12111f5c5 100644
> --- a/include/linux/sysfs.h
> +++ b/include/linux/sysfs.h
> @@ -105,7 +105,10 @@ struct attribute_group {
> size_t (*bin_size)(struct kobject *,
> const struct bin_attribute *,
> int);
> - struct attribute **attrs;
> + union {
> + struct attribute **attrs;
> + const struct attribute *const *attrs_new;
> + };
I'm all for the idea, BUT, let's finish up doing this one:
> union {
> struct bin_attribute **bin_attrs;
> const struct bin_attribute *const *bin_attrs_new;
first please.
That way we can see just how "easy" the switch from _new to not-new goes :)
thanks,
greg k-h
next prev parent reply other threads:[~2025-01-17 7:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-16 17:32 [PATCH 0/6] sysfs: prepare the constification of struct attribute Thomas Weißschuh
2025-01-16 17:32 ` [PATCH 1/6] sysfs: attribute_group: allow registration of const attribute Thomas Weißschuh
2025-01-17 7:01 ` Greg Kroah-Hartman [this message]
2025-06-28 8:19 ` Thomas Weißschuh
2025-06-28 8:30 ` Greg Kroah-Hartman
2025-01-16 17:32 ` [PATCH 2/6] sysfs: transparently handle const pointers in ATTRIBUTE_GROUPS() Thomas Weißschuh
2025-01-16 17:32 ` [PATCH 3/6] sysfs: introduce __SYSFS_FUNCTION_ALTERNATIVE() Thomas Weißschuh
2025-01-16 17:32 ` [PATCH 4/6] sysfs: attribute_group: enable const variants of is_visible() Thomas Weißschuh
2025-01-16 17:32 ` [PATCH 5/6] samples/kobject: add is_visible() callback to attribute group Thomas Weißschuh
2025-01-16 17:32 ` [PATCH 6/6] samples/kobject: constify 'struct foo_attribute' Thomas Weißschuh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2025011714-skeleton-bring-3e77@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=rafael@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox