From: Ondřej Surý <ondrej@isc.org>
Date: Mon, 5 Aug 2024 10:24:53 +0000 (+0000)
Subject: chg: dev: call rcu_barrier() in the isc_mem_destroy() just once
X-Git-Tag: alessio/regression/a26055f03e~5
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=dcee04f70cbf17ade03b1831eeab8a87c73a54a9;p=thirdparty%2Fbind9.git

chg: dev: call rcu_barrier() in the isc_mem_destroy() just once

The previous work in this area was led by the belief that we might be
calling call_rcu() from within call_rcu() callbacks.  After carefully
checking all the current callback, it became evident that this is not
the case and the problem isn't enough rcu_barrier() calls, but something
entirely else.

Call the rcu_barrier() just once as that's enough and the multiple
rcu_barrier() calls will not hide the real problem anymore, so we can
find it.

Merge branch '4607-call-a-single-rcu_barrier' into 'main'

See merge request isc-projects/bind9!9134
---

dcee04f70cbf17ade03b1831eeab8a87c73a54a9