Messages in this thread | | | From | David Howells <> | Subject | Re: [PATCH] Mark i2o config broken on 64-bit platforms. | Date | Wed, 09 Jul 2008 17:18:18 +0100 |
| |
Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> 64bit kernel 32bit user space should be fine,
There's a place I pointed out in an earlier email where it appears a 64-bit kernel can screw up, even with a 32-bit userspace. It allocates a piece of RAM with kmalloc(), takes the address of it, passes that through virt_to_bus(), discards the upper 32-bits from the result and posts it in an I2O message, presumably to the device. That would appear likely to go kaboom on a 64-bit system with more than 4GB of RAM.
If the device doesn't use that address, then why pass it at all?
David
| |