Zach Brown 7854471475 scoutfs: fix server wq destory warning ...

We were seeing warnings in destroy_workqueue() which meant that work was
queued on the server workqueue after it was drained and before it was
finally destroyed.

The only work that wasn't properly waited for was the commit work.  It
looks like it'd be idle because the server receive threads all wait for
their request processing work to finish.  But the way the commit work is
batched means that a request can have its commit processed by executing
commit work while leaving the work queued for another run.

Fix this by specifically waiting for the commit work to finish after the
server work has waited for all the recv and compaction work to finish.

I wasn't able to reliably trigger the assertion in repeated xfstests
runs.  This survived many runs also, let's see if it stops the
destroy_workqueue() assertion from triggering in the future.

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

2017-09-12 15:22:03 -07:00

..

Documentation

Flesh out some pieces of the scoutfs.md doc

2017-04-18 13:51:10 -07:00

src

scoutfs: fix server wq destory warning

2017-09-12 15:22:03 -07:00

.gitignore

scoutfs: remove our copy of the dlm

2017-07-19 13:30:03 -07:00

Makefile

scoutfs: add git describe to built module

2017-08-03 15:07:23 -07:00