Our application
In basic terms our IoT collection device reads data from a sensor, it processes this signal and then runs it through a neural network and then sends the output to another device in the near vicinity.
Sensor Reading > Data filter > Neural Network > transmitter.
We use the standard c++ deque to share data between these different modules.
First run using Cheri
Now that we have compiled our program to work with Cheri we will run it and see if we encounter any errors while running it.
On the first run we encountered this above issue, so it looks like there is a potential security issues in this early version of our code. Below we will start debugging the issue.
Debugging the issue
Before debugging it is important to compile the application with debug flags with adds extra information to the binary which will help us debug. (-g when compiling directly or -DCMAKE_BUILD_TYPE=Debug when usinng CMake)
Next we just use gdb to run the application to see if we get a more verbose error, this then should give us a clue where to look for the problem.
So it looks like the actual problem is a bounds fault, as shown above the issue seems to link to register ca2, gdb will also supply a line number and file name where the exception occurred. if we run disas this shows us the assembly command that caused the exception. It looks like the CPU is trying to load a word from register a2 into a4 when the fault occurs.
gdb tells us that the issue occurs at line 300 in a file we use to do some of the data filtering, below is a screenshot of the offending piece of code. The value x is passed is passed in as an argument to this function, the goal of this function is to provide the inverse square root of the input value.
Looking at line 300 it looks like it tries to cast y into a long. This code works on the assumption that the sizeof(long) and sizeof(float) are equal on the target platform. We are running this inside the riscv64-purecap VM, in risv64 a long is 8 bytes and a float is 4 bytes which is why we are getting the capability bounds error.
Background to the issue we have found
This method of doing inverse square root is actually quite we documented and was initially used to get around the lack of instructions to do this efficiently. The SSE instruction set helped greatly with this meaning it no longer needs to be done this way on most machines.
https://en.wikipedia.org/wiki/Fast_inverse_square_root
However there may still be some use cases to this in lower powered embedded hardware with limited instruction sets. So this may need to be included on certain versions of our device or we may need to look into using the sqrt function from the C++ library to make this code more platform agnostic.
Use of this may also be considered an aliasing violation as explained below:
https://stackoverflow.com/questions/98650/what-is-the-strict-aliasing-rule
