On Wed, Feb 25, 2015 at 02:14:55PM -0800, Laura Abbott wrote: > > The set_memory_* functions currently only support module > addresses. The addresses are validated using is_module_addr. > That function is special though and relies on internal state > in the module subsystem to work properly. At the time of > module initialization and calling set_memory_*, it's too early > for is_module_addr to work properly so it always returns > false. Rather than be subject to the whims of the module state, > just bounds check against the module virtual address range. > > Signed-off-by: Laura Abbott <lau...@codeaurora.org>
Not sure which tree this would be merged through, so: Acked-by: Catalin Marinas <catalin.mari...@arm.com> I can pick up the arm64 patch and the module.c one with Rusty's ack (as for the arm one, I think it could go in via rmk's patch system). -- Catalin -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/