Kent Overstreet ee526b88ca closures: Fix race in closure_sync()
As pointed out by Linus, closure_sync() was racy; we could skip blocking
immediately after a get() and a put(), but then that would skip any
barrier corresponding to the other thread's put() barrier.

To fix this, always do the full __closure_sync() sequence whenever any
get() has happened and the closure might have been used by other
threads.

Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
2023-10-30 21:48:22 -04:00
..
2023-09-01 16:54:25 -07:00
2023-09-01 12:21:32 -07:00
2023-09-01 16:54:25 -07:00
2023-10-30 13:12:15 -10:00
2023-10-30 13:12:15 -10:00
2023-09-02 08:25:19 +01:00