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]
Date:	Thu, 16 Oct 2008 14:46:45 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Josh Boyer <jwboyer@...ux.vnet.ibm.com>
Cc:	davem@...emloft.net, alan@...hat.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] serial: Make uart_port's ioport "resource_size_t"

On Tue, 14 Oct 2008 12:26:21 -0400
Josh Boyer <jwboyer@...ux.vnet.ibm.com> wrote:

> Recently uart_port's iobase was changed to be an 'unsigned
> long' to avoid chopping off the upper 32-bits of the
> address on 64-bit CPUs.  However, there are CPUs that are
> 32-bit but have a 64-bit address space.  This changes
> iobase to be 'resource_size_t' to accommodate those types
> of systems.  This also matches what is done for the mapbase
> member of uart_port.
> 
> Signed-off-by: Josh Boyer <jwboyer@...ux.vnet.ibm.com>
> 
> ---
> 
> diff --git a/include/linux/serial_core.h b/include/linux/serial_core.h
> index e27f216..cb0185b 100644
> --- a/include/linux/serial_core.h
> +++ b/include/linux/serial_core.h
> @@ -241,7 +241,7 @@ typedef unsigned int __bitwise__ upf_t;
>  
>  struct uart_port {
>  	spinlock_t		lock;			/* port lock */
> -	unsigned long		iobase;			/* in/out[bwl] */
> +	resource_size_t		iobase;			/* in/out[bwl] */
>  	unsigned char __iomem	*membase;		/* read/write[bwl] */
>  	unsigned int		irq;			/* irq number */
>  	unsigned int		uartclk;		/* base uart clock */

This will of course require that all now-broken printk()s be unbroken. 
I spot two in serial_core.c alone.

--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ