Description

kASLR is a handy security feature, with no performance downside. (The only downside is some slight inconvenience if you're using KGDB, but if you're the type of person who does kernel step debugging, it seems sane to guess you're already building your own kernel.)

If it cannot be enabled due to lack of seed, the kernel will simply print a warning and continue. (See #4306 for more context on what was previously added to get it working on a NanoPi R4S.) I also believe this warning will be useful note for us to add rng support on all devices as time goes on.

Example of failure:

[    0.052888] KASLR disabled due to lack of seed

Example of success (on a NanoPi R4S):

[    0.078587] KASLR enabled

How Has This Been Tested?

• [x] It's been enabled and stressed tested on a NanoPi R4S

Checklist:

• [x] My code follows the style guidelines of this project
• [x] I have performed a self-review of my own code
• [ ] I have commented my code, particularly in hard-to-understand areas
• [ ] I have made corresponding changes to the documentation
• [ ] My changes generate no new warnings
• [x] Any dependent changes have been merged and published in downstream modules

View the full article