Originally Posted by demolition
So it could potentially still break under certain unlucky conditions?
I don't assume that you can disable interrupts during access when operating in WB?
forbid() is always available, also under WB. It should not be disabled too long, but it is meant exactly for things like this: Make an action atomic, because other actions may interfere with it. Unfortunately, a semaphore doesn't do the job here, as you can badly mess with the ACA620 memory layout ;-)
So no, if implemented the right way, it doesn't crash.