| commit | 735aa900e4bf57b777ac620bed7c88234ec4b601 | |
| author | Max Filippov <jcmvbkbc@gmail.com> | |
| Wed, 19 May 2021 10:40:00 +0000 (19 03:40 -0700) | ||
| committer | Max Filippov <jcmvbkbc@gmail.com> | |
| Thu, 20 May 2021 20:02:58 +0000 (20 13:02 -0700) | ||
| tree | 475a9040b184c4c1291ff11cb725941ff0447b87 | treesnapshot (tar.gz zip) |
| parent | cb2d627a00a6bf686bc221b05f136545639a1c37 | commitdiff |
target/xtensa: fix access ring in l32ex
l32ex does memory access as all regular load/store operations at CRING
level. Fix apparent pasto from l32e that caused it to use RING instead.
This is a correctness issue, not a security issue, because in the worst
case the privilege level of memory access may be lowered, resulting in
an exception when the correct implementation would've succeeded.
In no case it would allow memory access that would've raised an
exception in the correct implementation.
Cc: qemu-stable@nongnu.org
Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
Signed-off-by: Max Filippov <jcmvbkbc@gmail.com>
l32ex does memory access as all regular load/store operations at CRING
level. Fix apparent pasto from l32e that caused it to use RING instead.
This is a correctness issue, not a security issue, because in the worst
case the privilege level of memory access may be lowered, resulting in
an exception when the correct implementation would've succeeded.
In no case it would allow memory access that would've raised an
exception in the correct implementation.
Cc: qemu-stable@nongnu.org
Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
Signed-off-by: Max Filippov <jcmvbkbc@gmail.com>
| target/xtensa/translate.c | diffblobblamehistory |