Vadim Kaushan

@jonas-schievink > you'd just smash the vector table instead of application data, which is hopefully more noticeable This sounds like a code execution vulnerability out of the box. Quite easy...

Anyway, I think it's a good idea to have this stack protection feature, but I'd also like to have a possibility for opt-out.

With the [new CriticalSection type](https://github.com/rust-embedded/bare-metal/pull/20) `interrupt::free()` should pass `CriticalSection` by value instead of by reference.

Definitely! You can copy the linker script from the corresponding `riscv-rt` source tree into your project under a different name and use it in `.cargo/config` instead of one provided by...

Change it to: ``` "-C", "link-arg=-Thifive1-memory.x", "-C", "link-arg=-Tnewlink.x" ``` (you also need to include memory definitions before the linker script)

Only if you need a different memory layout or you do not have a bootloader.

Region aliases are different things, they were added to prevent hardcoding `FLASH` everywhere and to allow some flexibility. If you have different `.textX` section names, you can try to group...

You don't need the first INCLUDE as you defined your own RAM regions, but other things look sane

Correct. Or you can create two different memory.x files, one for M-mode and one for U-mode and use them to link two different binaries with the same (possibly modified) link.x...

Yes, you're right.