linux-kernel - Re: UIO support for >32-bit physical addresses on 32-bit platforms

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: <20100223150140.GA3781@suse.de>
Date:	Tue, 23 Feb 2010 07:01:41 -0800
From:	Greg KH <gregkh@...e.de>
To:	Kumar Gala <galak@...nel.crashing.org>
Cc:	hjk@...utronix.de,
	"linux-kernel@...r.kernel.org List" <linux-kernel@...r.kernel.org>
Subject: Re: UIO support for >32-bit physical addresses on 32-bit platforms

On Tue, Feb 23, 2010 at 08:54:16AM -0600, Kumar Gala wrote:
> Hans, Greg,
> 
> We are looking at using UIO for some driver work and noticed it
> assumes the address for MMIO regions is an 'unsigned long'.  This is a
> problem for the platforms we have in which we support a 36-bit
> physical address in a 32-bit machine.
> 
> Should we just change addr/size in struct uio_mem to u64 always?  At
> first I was thinking phys_addr_t but realized the addr could be PHYS,
> LOGICAL, or VIRTUAL.

I think that would work out fine, Hans, any ideas if this would cause
any problems with existing code or not?

thanks,

greg k-h
--
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/