Vladimír Čunát authored 9 months ago and Oto Šťáva committed 8 months ago

- Upstream last maintained 3.0.x in summer 2022.
- Our packaging shouldn't be affected, neither the new one, nor OBS.
- If someone updates resolver, it shouldn't be too hard
  to update libknot as well.
- Maintenance on resolver side still needed effort for kres-gen-30.lua

manager: recovery from 'policy-loader' failure during reload

See merge request !1563

manager: policy-loader: new process for loading policy rules separately

See merge request !1540

Basically, the reset is necessary when only the policy rules have changed and there is no need to update the workers config.

The main reason for this is to load the policies before the canary worker starts, making it a prerequisite for starting the workers.

When starting the resolver, we wait for policy-loader until policy rules are successfully loaded into the cache where the rules are shared between kred workers. After that, other processes are started. Otherwise, the workers might start without the configured rules in the cache while they are already resolving DNS traffic.

Vladimír Čunát authored 10 months ago and Aleš Mrázek committed 8 months ago

Let's avoid reloading the RO transaction unless necessary.
For example, when normal config reload happens (one kresd at a time),
we most likely do *not* want to reload the rule DB prematurely.

daemon/tls: print IP when failing certificate check

See merge request knot/knot-resolver!1560

daemon: use __attribute__((constructor)) for protolayer_globals

See merge request !1559

The `protolayer_globals` array can basically be treated as a constant by
most of the program and its initialization only uses compile-time-known
values.  We basically only initialize parts of the array in different
files throughout the codebase to maintain separation of concerns, so
that each piece of Knot Resolver initializes the part that pertains to
it.  Therefore, I believe that it is more ergonomic to just use
`__attribute__((constructor))` for these functions, so as not to pollute
`daemon/main.c` with these calls.

manager: directory cleaning

See merge request !1557