Navigating through the kernel source with architecture and sub-architectures requires that 'maps' rules are applied in a definite order since they are cumulative.
Remapping rules are stored in Perl hash. Application is requested by a "for each (%maps)" instruction which pulls the rule in random order ("to protect against attacks", Perldoc says). The consequence is the order of the rules is not preserved, thus some dependent rules may be applied before the master rule and they will fail.
However, it may work correctly sometimes which hides the bug. Anyway, this is not satisfactory.
Suggestion: change rules storage from hash to array to control the application order.
Is there an impact on performance?
Log in to post a comment.