linux-kernel - 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-next>] [day] [month] [year] [list]

Message-Id: <A596AEB5-BAF0-4BF9-A9C0-44C50B9BCA34@kernel.crashing.org>
Date:	Tue, 23 Feb 2010 08:54:16 -0600
From:	Kumar Gala <galak@...nel.crashing.org>
To:	hjk@...utronix.de, Greg Kroah-Hartman <gregkh@...e.de>
Cc:	"linux-kernel@...r.kernel.org List" <linux-kernel@...r.kernel.org>
Subject: UIO support for >32-bit physical addresses on 32-bit platforms

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.

- k

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