fuzz: Add a linker fuzzer #252
Conversation
We add a fuzzer for the linker, that uses RISC-V instruction encoding logic to create a sequence of valid instructions. Which then is compiled into a ELF binary and passed to the linker. Expectation here is that the fuzzer would always generate a valid ELF binary with valid instructions, and the linker should be able to link it without any issues. Currently the ELF binary is limited to one section (.text) and no symbols. We may want to extend that in the future. Signed-off-by: Aman <aman@parity.io>
|
This is the PR that I get notifications for that lead to 403 error every week for some reason... I.e. the one I was talking about last year in Matrix. I'll put a screenshot next time this happens. It's a different PR with the name "fuzz: interpreter" by @subotic. I've gotten every single week since last year notifications from it. This explains the confusion. @subotic Do you know what is going on? I get almost every a notification. When I click it, Github says that there is zero files changed. I can live with that glitch but it is just bit weird... |
No need for apologies, I was just wondering what it is :-) They did not appear for some time but I got notification again last week. Not Github expert so thus just plain asking... |
We add a fuzzer for the linker, that uses RISC-V instruction encoding logic to create a sequence of valid instructions. Which then is compiled into a ELF binary and passed to the linker.
Expectation here is that the fuzzer would always generate a valid ELF binary with valid instructions, and the linker should be able to link it without any issues.
Currently the ELF binary is limited to one section (.text) and no symbols. We may want to extend that in the future.
Note: I saw some crashes that the fuzzer has reported and I am working on investigating those issues.