log_check / tainted_check failed in ubuntu_boot because of warnings (Found insecure W+X mapping at address) found on F/G/H-riscv

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1905728

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Still seeing this with the 5.8.0-17-generic riscv kernel on groovy. See attached dmesg.

This is not a regression and has been this way since the dawn of 5.8 riscv, as we have CONFIG_STRICT_KERNEL_RWX set.

When investigating, I see many fixes that involve the linker script, so I assume this is due to some sections, like init sections carrying both text and data, which could cause this.

I tried picking a lot of commits, and needed to either do extensive backports or carry a lot of commits, and still without success, hitting a linker problem that would require carrying even more fixes.

So, contrary to what has been said about 5.8 bringing up STRICT_KERNEL_RWX to riscv, this is really not ready for prime time, and should be left for future versions.

TL;DR: We should just disable CONFIG_STRICT_KERNEL_RWX on linux-riscv 5.8.

Cascardo.

Observed on G/RISC-V , cycle sru-20210510 .

Observed on G/RISC-V , cycle sru-20210531 .

There is a thread here:
https://<email address hidden>/T/

Looks like this has landed:
https://github.com/torvalds/linux/commit/8a4102a0cf07cc76a18f373f6b49485258cc6af4#diff-2db30a5588193fbb572fc2b96f3b47ae2e7e83351c5122c368b2b6fa56f38cda

And here is another patch from Alex, another fix to 2bfc6cd
("riscv: Move kernel mapping outside of linear mapping") as well.
https://github.com/torvalds/linux/commit/e5c35fa0401971701dcd7675f471b664698244dd#diff-2db30a5588193fbb572fc2b96f3b47ae2e7e83351c5122c368b2b6fa56f38cda

The Groovy Gorilla has reached end of life, so this bug will not be fixed for that release

v5.13 in impish-proposed has this fixed on riscv.

it will not be backported to earlier series, hence marking hirsute as wontfix.