Can't access a partition that was locked by a crashed process #31

New Issue

Sweetbread · 2024-03-09T20:07:36+01:00

Sweetbread commented

2024-03-09 20:07:36 +01:00

Current FS code works like this: lock (a mutex guarding access to) a partition, read/write data, unlock the partition.
When a thread crashes while reading/writing, the partition is left locked. Therefore other programs can't acquire the lock and access that partition anymore.

In theory, kernel could release acquired locks when threads crash. In practice, kernel has no idea what locks have been acquired by a given thread.
It is possilble to modify FS code to fill an array of acquired locks. In fact, this is very similar to an array of file descriptors.

So, resolution of this issue could be a side effect of file descriptors when they are implemented.

Additional information:
https://board.kolibrios.org/viewtopic.php?f=31&t=3397&start=150#p76785

dunkaist

Current FS code works like this: lock (a mutex guarding access to) a partition, read/write data, unlock the partition. When a thread crashes while reading/writing, the partition is left locked. Therefore other programs can't acquire the lock and access that partition anymore. In theory, kernel could release acquired locks when threads crash. In practice, kernel has no idea what locks have been acquired by a given thread. It is possilble to modify FS code to fill an array of acquired locks. In fact, this is very similar to an array of file descriptors. So, resolution of this issue could be a side effect of file descriptors when they are implemented. **Additional information**: https://board.kolibrios.org/viewtopic.php?f=31&t=3397&start=150#p76785 --- *dunkaist*

Sweetbread added the

labels 2024-03-09 20:07:46 +01:00

Sweetbread added this to the 0.9.0.0 milestone 2024-03-10 20:18:43 +01:00

Sweetbread added the

Category/Kernel