Zach Brown 7720222588 Have statfs use unlocked stable roots ...

The server's statfs request handler was intending to lock dirty
structures as they were walked to get sums used for statfs fields.
Other callers walk stable structures, though, so the summation calls had
grown iteration over other structures that the server didn't know it had
to lock.

This meant that the server was walking unlocked dirty structures as they
were being modified.  The races are very tight, but it can result in
request handling errors that shut down connections and IO errors from
trying to read inconsistent refs as they were modified by the locked
writer.

We've built up infrastructure so the server can now walk stable
structures just like the other callers.  It will no longer wander into
dirty blocks so it doesn't need to lock them and it will retry if its
walk of stale data crosses a broken reference.

Signed-off-by: Zach Brown <zab@versity.com>

2022-12-12 14:59:22 -08:00

..

src

Have statfs use unlocked stable roots

2022-12-12 14:59:22 -08:00

.gitignore

scoutfs: update rpm building infrastructure

2018-09-14 15:07:10 -07:00

Makefile

Filesystem version instead of format hash check

2021-01-15 10:53:00 -08:00

scoutfs-kmod.spec.in

scoutfs: update rpm building infrastructure

2018-09-14 15:07:10 -07:00