public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Niklas Cassel <cassel@kernel.org>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Cc: Damien Le Moal <dlemoal@kernel.org>,
	linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
	linux-ide@vger.kernel.org
Subject: Re: [PATCH] ata: Constify struct pci_device_id
Date: Mon, 18 Nov 2024 12:42:58 +0100	[thread overview]
Message-ID: <ZzsoQlOaDP4FJ8G-@ryzen> (raw)
In-Reply-To: <8bddfee7f6f0f90eeb6da7156e30ab3bd553deb1.1731704917.git.christophe.jaillet@wanadoo.fr>

On Fri, Nov 15, 2024 at 10:08:55PM +0100, Christophe JAILLET wrote:
> 'struct pci_device_id' is not modified in these drivers.
> 
> Constifying this structure moves some data to a read-only section, so
> increase overall security.
> 
> On a x86_64, with allmodconfig, as an example:
> Before:
> ======
>    text	   data	    bss	    dec	    hex	filename
>    4245	   1454	      4	   5703	   1647	drivers/ata/ata_generic.o
> 
> After:
> =====
>    text	   data	    bss	    dec	    hex	filename
>    4725	    974	      4	   5703	   1647	drivers/ata/ata_generic.o
> 
> Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
> ---
> Compile tested-only.
> ---
> ---
>  drivers/ata/ata_generic.c  | 2 +-
>  drivers/ata/pata_atp867x.c | 2 +-
>  drivers/ata/pata_piccolo.c | 2 +-
>  3 files changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/ata/ata_generic.c b/drivers/ata/ata_generic.c
> index 2f57ec00ab82..e70b6c089cf1 100644
> --- a/drivers/ata/ata_generic.c
> +++ b/drivers/ata/ata_generic.c
> @@ -209,7 +209,7 @@ static int ata_generic_init_one(struct pci_dev *dev, const struct pci_device_id
>  	return ata_pci_bmdma_init_one(dev, ppi, &generic_sht, (void *)id, 0);
>  }
>  
> -static struct pci_device_id ata_generic[] = {
> +static const struct pci_device_id ata_generic[] = {
>  	{ PCI_DEVICE(PCI_VENDOR_ID_PCTECH, PCI_DEVICE_ID_PCTECH_SAMURAI_IDE), },
>  	{ PCI_DEVICE(PCI_VENDOR_ID_HOLTEK, PCI_DEVICE_ID_HOLTEK_6565), },
>  	{ PCI_DEVICE(PCI_VENDOR_ID_UMC,    PCI_DEVICE_ID_UMC_UM8673F), },
> diff --git a/drivers/ata/pata_atp867x.c b/drivers/ata/pata_atp867x.c
> index aaef5924f636..308f86f9e2f0 100644
> --- a/drivers/ata/pata_atp867x.c
> +++ b/drivers/ata/pata_atp867x.c
> @@ -525,7 +525,7 @@ static int atp867x_reinit_one(struct pci_dev *pdev)
>  }
>  #endif
>  
> -static struct pci_device_id atp867x_pci_tbl[] = {
> +static const struct pci_device_id atp867x_pci_tbl[] = {
>  	{ PCI_VDEVICE(ARTOP, PCI_DEVICE_ID_ARTOP_ATP867A),	0 },
>  	{ PCI_VDEVICE(ARTOP, PCI_DEVICE_ID_ARTOP_ATP867B),	0 },
>  	{ },
> diff --git a/drivers/ata/pata_piccolo.c b/drivers/ata/pata_piccolo.c
> index ced906bf56be..beb53bd990be 100644
> --- a/drivers/ata/pata_piccolo.c
> +++ b/drivers/ata/pata_piccolo.c
> @@ -97,7 +97,7 @@ static int ata_tosh_init_one(struct pci_dev *dev, const struct pci_device_id *id
>  	return ata_pci_bmdma_init_one(dev, ppi, &tosh_sht, NULL, 0);
>  }
>  
> -static struct pci_device_id ata_tosh[] = {
> +static const struct pci_device_id ata_tosh[] = {
>  	{ PCI_DEVICE(PCI_VENDOR_ID_TOSHIBA,PCI_DEVICE_ID_TOSHIBA_PICCOLO_1), },
>  	{ PCI_DEVICE(PCI_VENDOR_ID_TOSHIBA,PCI_DEVICE_ID_TOSHIBA_PICCOLO_2),  },
>  	{ PCI_DEVICE(PCI_VENDOR_ID_TOSHIBA,PCI_DEVICE_ID_TOSHIBA_PICCOLO_3),  },
> -- 
> 2.47.0
> 

Looks good to me:
Reviewed-by: Niklas Cassel <cassel@kernel.org>

However, since we are in the middle of the merge window, expect to wait
until 6.13-rc1 is out until this is picked up.


Kind regards,
Niklas

  parent reply	other threads:[~2024-11-18 11:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-15 21:08 [PATCH] ata: Constify struct pci_device_id Christophe JAILLET
2024-11-17 13:04 ` Sergey Shtylyov
2024-11-18 11:42 ` Niklas Cassel [this message]
2024-12-03  4:16 ` Niklas Cassel

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=ZzsoQlOaDP4FJ8G-@ryzen \
    --to=cassel@kernel.org \
    --cc=christophe.jaillet@wanadoo.fr \
    --cc=dlemoal@kernel.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@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