Eric Dumazet <eric.duma...@gmail.com> wrote: > Just use RCU : A writer is supposed to work on a private copy, and > _then_ publish the new pointer, so that a reader can not see mangled > string. > > We either copy the 'old' name or the 'new' one. > > A seqcount is not needed, and wont prevent you from reading the value > right before a change anyway.
Would you rather use kfree_rcu or unconditional synchronize_net() before releasing old memory?
