linux-kernel - Re: [PATCH] pci: 64bit resource fix in setup-res.c

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAErSpo5wdxqc7w0Zn-Z9-Uog8GyDqJytV5a5Uxdf39BwaXF2Hw@mail.gmail.com>
Date:	Wed, 11 Jul 2012 17:12:53 -0600
From:	Bjorn Helgaas <bhelgaas@...gle.com>
To:	Nikhil P Rao <nikhil.rao@...el.com>
Cc:	linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	Yinghai Lu <yinghai@...nel.org>
Subject: Re: [PATCH] pci: 64bit resource fix in setup-res.c

On Wed, Jun 20, 2012 at 1:56 PM, Nikhil P Rao <nikhil.rao@...el.com> wrote:
> size parameter of _pci_assign_resource() needs to be
> of type resource_size_t rather than int
>
> Signed-off-by: Nikhil P Rao <nikhil.rao@...el.com>
> ---
>  drivers/pci/setup-res.c |    3 ++-
>  1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/pci/setup-res.c b/drivers/pci/setup-res.c
> index eea85da..9f6bbec 100644
> --- a/drivers/pci/setup-res.c
> +++ b/drivers/pci/setup-res.c
> @@ -206,7 +206,8 @@ static int pci_revert_fw_address(struct resource *res, struct pci_dev *dev,
>         return ret;
>  }
>
> -static int _pci_assign_resource(struct pci_dev *dev, int resno, int size, resource_size_t min_align)
> +static int _pci_assign_resource(struct pci_dev *dev, int resno,
> +               resource_size_t size, resource_size_t min_align)
>  {
>         struct resource *res = dev->resource + resno;
>         struct pci_bus *bus;

I applied this, thanks!  Sorry it took so long.

Bjorn
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/