linaro-swg/optee_android_manifest

Communication error between Linux and OPTEE - memory mapping changed in kernel ?

ppeiffer-invn opened this issue · 5 comments

ppeiffer-invn commented

Hi,

My env is Android 7.1 + OPTEE 3.0 on HiKey (based on a previous manifest version from this repo)
I use a fixed version of the bootloader components.
But I'm pointing on the branch android-hikey-linaro-4.9 for the Linux kernel which keeps moving

I noticed that a change done in Linux kernel the last 2 months broke the communication between Linux and OPTEE OS
From what I found so far, looks like there is memory mapping change somewhere... ?

Am I correct ? If yes, can someone point me to some solution to recover this or how to fix this ? (I didn't find any changes in optee-os that seems to fix this)

Thanks,

jbech-linaro commented

Hi, you are probably right here. We haven't had any automatic CI/test for the AOSP + OP-TEE builds (something we are about to improve) and in addition to that we have no engineer available to focus on this for the moment, so currently this has been a best effort work done by @vchong . All this together unfortunately means that the OP-TEE + AOSP builds breaks from time to time. As mentioned, we want to fix this in a better way in the future, but right now we have a couple of other ares which has higher priority, so this unfortunately have to wait.

If you have time and want to contribute, then you could try syncing up things to latest in the OP-TEE gits / branches / patches that are being used in this setup and then submit updated patches for this. We would be more than happy if that would happen.

vchong commented

@ppeiffer We're aware of the issue (see 6a21728 for temp/hack workaround) and trying to find opportunities to look into it, but it should still have been working about a month ago (the changes in Linux kernel were merged on 2/21: https://android-git.linaro.org/kernel/hikey-linaro.git/log/?h=android-hikey-linaro-4.9&qt=grep&q=TEE), so wondering why you're saying 2 months? Do you have any other info regarding this issue? As @jbech-linaro said, we'd appreciate any help we can get right now.

Other workarounds you can try are 1. remove the tee-related kernel changes merged on 2/21, or 2. use a version of the kernel before the 2/21 changes got merged.

ppeiffer-invn commented

Thanks for that; I'm speaking about 2 months ago just because I didn't update my env in the meantime.

I'll try to have a look with the time I have.

P.

jbech-linaro commented

That would be great @ppeiffer and would help us a lot, thanks!

vchong commented

@ppeiffer this has been fixed. Please re-open if you still have issues.

  • 👍1