* Borislav Petkov <[email protected]> wrote:
> thanks for the report.
>
> So, AFAICT, this is caused by ksysfs ioremapping struct
> setup_data for a short time so that it can count it and
> show it in /sys/kernel/boot_params/setup_data/*
>
> And, of course, the setup_data thing which we're using
> for kaslr param passing is RAM and ioremap complains.
>
> And currently I don't have a good idea how to fix it.
> Perhaps introduce an ioremap_* something which suppresses
> the warning as we're going to iounmap() right afterwards
> but that's ugly.
Why is it ioremap()-ed to begin with, why cannot the kernel
access its own data structure in RAM directly?
Thanks,
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
