From: Jonathan Cameron <jic23@kernel.org>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Cc: "David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-iio@vger.kernel.org
Subject: Re: [PATCH] iio: core: Constify struct configfs_item_operations and configfs_group_operations
Date: Wed, 31 Dec 2025 17:20:11 +0000 [thread overview]
Message-ID: <20251231172011.7e0b3cd1@jic23-huawei> (raw)
In-Reply-To: <6f327beea525e2b96724b0b395f1105ff7ccc305.1767007641.git.christophe.jaillet@wanadoo.fr>
On Mon, 29 Dec 2025 12:27:43 +0100
Christophe JAILLET <christophe.jaillet@wanadoo.fr> wrote:
> 'struct configfs_item_operations' and 'configfs_group_operations' are not
> modified in this driver.
>
> Constifying these structures moves some data to a read-only section, so
> increases overall security, especially when the structure holds some
> function pointers.
>
> On a x86_64, with allmodconfig:
> Before:
> ======
> text data bss dec hex filename
> 5037 1528 64 6629 19e5 drivers/iio/industrialio-sw-device.o
> 5509 1528 64 7101 1bbd drivers/iio/industrialio-sw-trigger.o
>
> After:
> =====
> text data bss dec hex filename
> 5133 1432 64 6629 19e5 drivers/iio/industrialio-sw-device.o
> 5605 1432 64 7101 1bbd drivers/iio/industrialio-sw-trigger.o
>
> Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Applied to the togreg branch of iio.git which I'll push out initially as testing
for 0-day to take a look at it.
Thanks,
Jonathan
prev parent reply other threads:[~2025-12-31 17:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-29 11:27 [PATCH] iio: core: Constify struct configfs_item_operations and configfs_group_operations Christophe JAILLET
2025-12-31 17:20 ` Jonathan Cameron [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=20251231172011.7e0b3cd1@jic23-huawei \
--to=jic23@kernel.org \
--cc=andy@kernel.org \
--cc=christophe.jaillet@wanadoo.fr \
--cc=dlechner@baylibre.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
/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