gocryptfs, branch v0.10

README: list today as v0.10 release date

2016-05-30T19:04:33+00:00

Also improve the order of the bullet points.

README: remove v0.10 release date (not yet released)

2016-05-30T07:40:16+00:00

The release has been delayed due to the fsstress issues that were hopefully fixed in the last commit.

fusefrontend: replace unreliable "fd < 0" check

2016-05-30T07:36:06+00:00

... with the "released" boolean. For some reason, the "f.fd.Fd() < 0" check did not work reliably, leading to nil pointer panics on the following wlock.lock(). The problem was discovered during fsstress testing and is unlikely to happen in normal operations. With this change, we passed 1700+ fsstress iterations.

toggledlog: wpanic: use Logger.Panic instead of naked panic

2016-05-30T07:26:59+00:00

This makes sure the panic message also ends up in syslog (if enabled).

fusefrontend: use sync.Once for one-time warnings

2016-05-29T20:50:03+00:00

Using a simple boolean was racy (which was harmless in this case) and non-idomatic.

fusefronted: check Fstat return value on file create

2016-05-29T20:43:48+00:00

The Fstat call should never fail, but still, if it does return an error it should be handled properly.

fusefrontend: simplify wlockMap

2016-05-29T20:40:05+00:00

mapMutex can be anonymous and using an RWMutex is overkill because the lock protects very short sections.

fsstress-loopback: properly stop on Ctrl-C

2016-05-29T11:57:22+00:00

Send fsstress (which ignores Ctrl-C) into the background so the shell gets the signal. Manually kill fsstress in the cleanup handler. Also, use the build.bash script for gocryptfs.

fusefrontend: remove unused "forgotten" variable

2016-05-29T11:46:47+00:00

The functionality has long been replaced by the fd < 0 check.

Update README for v0.10

2016-05-24T22:28:22+00:00

Also add dates for all releases.