From: "Gabriel L. Somlo" <somlo@cmu.edu>
To: Hongbo Li <lihongbo22@huawei.com>
Cc: mst@redhat.com, qemu-devel@nongnu.org
Subject: Re: [PATCH -next] fw_cfg: Constify struct kobj_type
Date: Wed, 18 Sep 2024 19:33:29 -0400 [thread overview]
Message-ID: <ZutjSVLNyBYRjIgg@errol.ini.cmu.edu> (raw)
In-Reply-To: <20240904011743.2010319-1-lihongbo22@huawei.com>
On Wed, Sep 04, 2024 at 09:17:43AM +0800, Hongbo Li wrote:
> This 'struct kobj_type' is not modified. It is only used in
> kobject_init_and_add() which takes a 'const struct kobj_type *ktype'
> parameter.
>
> Constifying this structure and moving it to a read-only section,
> and this can increase over all security.
>
> ```
> [Before]
> text data bss dec hex filename
> 5974 1008 96 7078 1ba6 drivers/firmware/qemu_fw_cfg.o
>
> [After]
> text data bss dec hex filename
> 6038 944 96 7078 1ba6 drivers/firmware/qemu_fw_cfg.o
> ```
>
> Signed-off-by: Hongbo Li <lihongbo22@huawei.com>
Acked-by: Gabriel L. Somlo <somlo@cmu.edu>
Thanks,
--Gabriel
> ---
> drivers/firmware/qemu_fw_cfg.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/firmware/qemu_fw_cfg.c b/drivers/firmware/qemu_fw_cfg.c
> index 5f43dfa22f79..85c525745b31 100644
> --- a/drivers/firmware/qemu_fw_cfg.c
> +++ b/drivers/firmware/qemu_fw_cfg.c
> @@ -452,7 +452,7 @@ static void fw_cfg_sysfs_release_entry(struct kobject *kobj)
> }
>
> /* kobj_type: ties together all properties required to register an entry */
> -static struct kobj_type fw_cfg_sysfs_entry_ktype = {
> +static const struct kobj_type fw_cfg_sysfs_entry_ktype = {
> .default_groups = fw_cfg_sysfs_entry_groups,
> .sysfs_ops = &fw_cfg_sysfs_attr_ops,
> .release = fw_cfg_sysfs_release_entry,
> --
> 2.34.1
>
prev parent reply other threads:[~2024-09-18 23:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-04 1:17 [PATCH -next] fw_cfg: Constify struct kobj_type Hongbo Li via
2024-09-18 23:33 ` Gabriel L. Somlo [this message]
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=ZutjSVLNyBYRjIgg@errol.ini.cmu.edu \
--to=somlo@cmu.edu \
--cc=lihongbo22@huawei.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).