On Wed, Feb 16, 2022 at 04:18:43PM +0100, Hannes Reinecke wrote: > My turn to be picky: > In the previous patch you use 'set_bit()' for GD_DEAD, which to my > knowledge doesn't imply a memory barrier. > Yet here you rely on that for the 'test_bit()' to return the correct/most > recent value. > Don't we need a memory barrier here somewhere? Well, we only do the test to skip useless work. A race is not a problem here.
