On Tue, Jul 21, 2020 at 02:33:03AM +0200, Marek wrote:
I'm on holidays right now, seeing the logs in my mobile I cannot infer much.
What's the memory map after the patch? Intentional? I mean the code/instruction region is read-only and executable and else read-write and non-executable?
May it happen that the tests try to write to instruction, read-only region? If failures then than it is on purpose.
If anything else needing a grater attention I'm sorry but it will have to probably wait until I'm back from holidays, about two weeks from now.
But thanks for looking through it. Our customers is keen on seeing the change in the Upstream.
I'm pretty sure we can work it out as all of the ARM SW suits, namely arm-trusted-firmware and ARM Linux kernel are using the notion of executable/non-executable and read-only/read-write.
I think this will have to wait for you to return from holidays and investigate more. All I know is that the QEMU models are working as expected prior to the patch and fail with it.