> I see, kfree does nothing with null pointers and direct return. > but again kfree is not a good suggestion. I have got the impression that the implementation detail is important here if non-null pointers (according to valid rescuer objects) are occasionally passed by the corresponding data structure member for the callback function “rcu_free_wq”. Can another clarification attempt reduce unwanted confusion for this patch review? Regards, Markus
