micrified / disasm Goto Github PK

The memory manager allows processes to initialize the shared file. This can go two ways.

1. The process is the first to try to access the file, in which case it creates it and installs the semaphore.
2. The process is not the first, in which case it opens the file and uses the internal data structures.

The race happens when the process which created the file is context-swapped out before it can install the infrastructure necessary to control access. Other processes will then try to use a non-initialized file.

Another problem occurs when the creating process runs it's full length, along with some other processes, and they terminate. The last process owning the file destroys it. If another file somehow opened this file but had yet to deposit it's "membership", then when it resumes execution it will crash because the file has been destroyed. I cannot foresee any good way to get around this right now. Somehow, I must account for all processes, not knowing when they will run, or how many there are.