Zygo Blaxell d5a99c2f5e roots: don't share a RootFetcher between threads ...

If the send workaround is enabled, it is possible for two threads (a
thread running the crawl_new task, and a thread attempting to apply the
send workaround) to access the same RootFetcher object at the same time.
That never ends well.

Give each function its own BtrfsRootFetcher object.

Fixes: https://github.com/Zygo/bees/issues/250
Signed-off-by: Zygo Blaxell <bees@furryterror.org>

2023-02-20 11:14:34 -05:00

..

.gitignore

bees: move usage message out of source file and fix a few inaccuracies

2020-12-17 17:54:51 -05:00

bees-context.cc

context: remove the one call to operator vector<> method in BtrfsIoctlLogicalInoArgs

2023-01-23 00:09:26 -05:00

bees-hash.cc

hash: don't spin when writes fail

2023-01-23 00:09:26 -05:00

bees-resolve.cc

types: member m_fd in BeesFileRange must be protected against data races

2021-12-19 15:10:02 -05:00

bees-roots.cc

roots: don't share a RootFetcher between threads

2023-02-20 11:14:34 -05:00

bees-thread.cc

context: get rid of all instances of pthread_cancel

2021-04-28 21:42:03 -04:00

bees-trace.cc

trace: use pthread_setname wrapper

2023-01-05 01:10:17 -05:00

bees-types.cc

BeesFileRange: coalesce is not used, subtract was never implemented

2022-12-20 20:50:59 -05:00

bees-usage.txt

bees: move usage message out of source file and fix a few inaccuracies

2020-12-17 17:54:51 -05:00

bees.cc

main: catch exceptions and exit gracefully

2023-01-05 01:10:17 -05:00

bees.h

roots: don't share a RootFetcher between threads

2023-02-20 11:14:34 -05:00

Makefile

src: bees-version.cc cleanups

2023-01-27 22:16:02 -05:00