Jakob Unterwurzacher f316f1b2df fusefronted: disallow writes running concurrently with reads ... 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.		2018-07-22 22:29:22 +02:00
..
open_file_table.go	fusefronted: disallow writes running concurrently with reads	2018-07-22 22:29:22 +02:00