On 3/25/25 06:56, Florian Westphal wrote: > Corubba Smith <corubba@xxxxxx> wrote: >> The dump_reset_handler will try to update the hashtable regardless of >> whether it is used (and thus initialized), which results in a segfault >> if it isn't. Instead just short-circuit the handler, and skip any >> further result processing because it's not used in this case anyway. >> All flow counters in conntrack are reset regardless of the return value >> of the handler/callback. > > How can this happen? > constructor_nfct (->start()) will return an error if ct_active table > cannot be allocated/is disabled? > In event mode the hashtable is optional, and sending SIGUSR2 to ulogd will call get_ctr_zero(). -- Corubba
