[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240617185026.lgpspvyjsygh4lry@DEN-DL-M70577>
Date: Mon, 17 Jun 2024 18:50:26 +0000
From: Daniel Machon <daniel.machon@...rochip.com>
To: Christophe JAILLET <christophe.jaillet@...adoo.fr>
CC: Horatiu Vultur <horatiu.vultur@...rochip.com>,
<UNGLinuxDriver@...rochip.com>, "David S. Miller" <davem@...emloft.net>,
"Eric Dumazet" <edumazet@...gle.com>, Jakub Kicinski <kuba@...nel.org>, Paolo
Abeni <pabeni@...hat.com>, Lars Povlsen <lars.povlsen@...rochip.com>, "Steen
Hegelund" <Steen.Hegelund@...rochip.com>, <linux-kernel@...r.kernel.org>,
<kernel-janitors@...r.kernel.org>, <netdev@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH net-next] net: microchip: Constify struct vcap_operations
> "struct vcap_operations" are not modified in these drivers.
>
> Constifying this structure moves some data to a read-only section, so
> increase overall security.
>
> In order to do it, "struct vcap_control" also needs to be adjusted to this
> new const qualifier.
>
> As an example, on a x86_64, with allmodconfig:
> Before:
> ======
> text data bss dec hex filename
> 15176 1094 16 16286 3f9e drivers/net/ethernet/microchip/lan966x/lan966x_vcap_impl.o
>
> After:
> =====
> text data bss dec hex filename
> 15268 998 16 16282 3f9a drivers/net/ethernet/microchip/lan966x/lan966x_vcap_impl.o
>
> Signed-off-by: Christophe JAILLET <christophe.jaillet@...adoo.fr>
> ---
> I hope this can be applied as a single patch.
> I think it can be split between lan966x, sparx5 and vcap if really needed.
> ---
LGTM.
Reviewed-by: Daniel Machon <daniel.machon@...rochip.com>
Powered by blists - more mailing lists