On 9/25/19 4:33 PM, Darrick J. Wong wrote: > From: Darrick J. Wong <darrick.wong@xxxxxxxxxx> > > Split the workqueue destroy function into two parts -- one to signal all > the threads to exit and wait for them, and a second one that actually > destroys all the memory associated with the workqueue. This mean we can > report latent workqueue errors independent of the freeing function. > > Signed-off-by: Darrick J. Wong <darrick.wong@xxxxxxxxxx> > --- > libfrog/workqueue.c | 37 ++++++++++++++++++++++++++++++------- > libfrog/workqueue.h | 2 ++ > repair/threads.c | 6 ++++++ > scrub/fscounters.c | 11 ++++++++++- > scrub/inodes.c | 5 +++++ > scrub/phase2.c | 5 +++++ > scrub/phase4.c | 6 ++++++ > scrub/read_verify.c | 1 + > scrub/spacemap.c | 5 +++++ > scrub/vfs.c | 5 +++++ > 10 files changed, 75 insertions(+), 8 deletions(-) Reviewed-by: Eric Sandeen <sandeen@xxxxxxxxxx>
