thanks for yet another clear explanation of a complex topic

The article contains the eagerly awaited Corbetian pun, but not for once a complaint about lack of Documentation/. That is unsurprising given the authors of the new feature.

The explanation suggests that the new feature is built on top of sequence locks (for hazptr_synchronize()), cleanup.h (for freeing the context) and cmpxchg (for updating and perhaps reading the slots). The kernel has accrued clever infrastructure which makes all kinds of cool new features easier to implement.

The fact that C++ has adopted hazard pointers before the kernel (https://en.cppreference.com/Template:cpp/synopsis/hazard_...) is surprising. Presumably McKenney et al. worked first on the C++ proposal given the ISO committee's slower release cycle.