From: Bodo Stroesser <bostroesser@gmail.com>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
"Martin K. Petersen" <martin.petersen@oracle.com>
Cc: linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-scsi@vger.kernel.org, target-devel@vger.kernel.org
Subject: Re: [PATCH] scsi: target: tcmu: Constify some structures
Date: Tue, 12 Nov 2024 14:49:55 +0100 [thread overview]
Message-ID: <e01952e3-8098-4490-a813-ed0d9457eb3e@gmail.com> (raw)
In-Reply-To: <f83cd8469cc17391178e1181e8c26c4c1fb6028f.1731330634.git.christophe.jaillet@wanadoo.fr>
On 11.11.24 14:10, Christophe JAILLET wrote:
> 'struct nla_policy' and 'struct match_table_t' are not modified in this
> driver.
>
> Constifying these structures moves some data to a read-only section, so
> increase overall security, especially when the structure holds some
> function pointers, which is the case of struct nla_policy.
>
> On a x86_64, with allmodconfig:
> Before:
> ======
> text data bss dec hex filename
> 93188 6933 338 100459 1886b drivers/target/target_core_user.o
>
> After:
> =====
> text data bss dec hex filename
> 93508 6581 338 100427 1884b drivers/target/target_core_user.o
>
> Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
> ---
> Compile tested only
> ---
> drivers/target/target_core_user.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/target/target_core_user.c b/drivers/target/target_core_user.c
> index 717931267bda..0f5d820af119 100644
> --- a/drivers/target/target_core_user.c
> +++ b/drivers/target/target_core_user.c
> @@ -361,7 +361,7 @@ static const struct genl_multicast_group tcmu_mcgrps[] = {
> [TCMU_MCGRP_CONFIG] = { .name = "config", },
> };
>
> -static struct nla_policy tcmu_attr_policy[TCMU_ATTR_MAX+1] = {
> +static const struct nla_policy tcmu_attr_policy[TCMU_ATTR_MAX + 1] = {
> [TCMU_ATTR_DEVICE] = { .type = NLA_STRING },
> [TCMU_ATTR_MINOR] = { .type = NLA_U32 },
> [TCMU_ATTR_CMD_STATUS] = { .type = NLA_S32 },
> @@ -2430,7 +2430,7 @@ enum {
> Opt_cmd_ring_size_mb, Opt_err,
> };
>
> -static match_table_t tokens = {
> +static const match_table_t tokens = {
> {Opt_dev_config, "dev_config=%s"},
> {Opt_dev_size, "dev_size=%s"},
> {Opt_hw_block_size, "hw_block_size=%d"},
Reviewed-by: Bodo Stroesser <bostroesser@gmail.com>
Thanks,
Bodo
next prev parent reply other threads:[~2024-11-12 13:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-11 13:10 Christophe JAILLET
2024-11-12 13:49 ` Bodo Stroesser [this message]
2024-11-21 2:55 ` Martin K. Petersen
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=e01952e3-8098-4490-a813-ed0d9457eb3e@gmail.com \
--to=bostroesser@gmail.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=target-devel@vger.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
all inboxes | Powered by JetHome®