Hi, On Wed, Feb 05, 2014 at 05:38:54PM +0100, Pali Rohár wrote: > > I assumed, that the workaround is not needed for this device type. > > That rx51 secure call must not be called on non secure devices (e.g. > qemu), because it cause kernel crash. So I thought that kernel should > write something like secure call is disabled on that device types. > Kernel code for errata 430973 will update ibe bit for non secure > devices. Do you see any advantage in having that message? > > I just added the warning for missing CONFIG_ARM_ERRATA_430973, > > because its very likely a misconfigured kernel. > > Yes, it can be misconfigured kernel, but if you do not have any thumb > binary (like stock Maemo 5 system), then it is safe and OK. I think running this kernel may also be a potential security problem. If I understand it right the ARM core is left in an unstable state when you run Thumb code, so this may result in funny effects in the kernel? -- Sebastian
Attachment:
signature.asc
Description: Digital signature
