| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2018-07-22 | fusefronted: disallow writes running concurrently with reads | Jakob Unterwurzacher | |
| As uncovered by xfstests generic/465, concurrent reads and writes could lead to this, doRead 3015532: corrupt block #1039: stupidgcm: message authentication failed, as the read could pick up a block that has not yet been completely written - write() is not atomic! Now writes take ContentLock exclusively, while reads take it shared, meaning that multiple reads can run in parallel with each other, but not with a write. This also simplifies the file header locking. | |||
| 2017-05-01 | openfiletable: rename WriteLock to ContentLock | Jakob Unterwurzacher | |
| ...and IDLock to HeaderLock. This matches what the locks actually protect. | |||
| 2017-05-01 | fusefronted, openfiletable: move the open file table to its own package | Jakob Unterwurzacher | |
| The open file table code needs some room to grow for the upcoming FD multiplexing implementation. | |||
