In the No26bitCode case (ie when abort handlers are entered in ABT32 mode), if...
In the No26bitCode case (ie when abort handlers are entered in ABT32 mode), if lazy task swapping was enabled and a data abort occurred that was not a page translation fault, then the code in AMB_LazyFixUp to map in the whole application slot was being circumvented, leading to problems for abort handlers in application space because r14_abt was corrupted by any abort due to accessing the abort handler itself. The test of the FSR (to compensate for the FAR being unusable for external aborts) which prompted the circumvention has therefore been moved inside AMB_LazyFixup. Also now preserves the FSR and FAR across AMB_LazyFixUp, so they are now visible from application abort handlers if desired. Version 5.35, 22.214.171.124. Tagged as 'Kernel-5_35-4_79_2_50'
Showing with 45 additions and 24 deletions