Bug#864341: systemd-sysctl: failed to apply sysctl config at bootup

[Arturo Borrero Gonzalez]

CC'ing Florian Westphal from Netfilter, kernel maintainer.

On Thu, 13 Jul 2017 12:27:10 +0200 Michael Biebl <biebl at debian.org> wrote:
> I think the proper solution is to find out why the /sys entries are not
> available after the module has been loaded and fix that in the conntrack
> module.
>

Is this the issue?
Perhaps the issue is that systemd is too quick between loading the
module and loading the sysctl config.
It has happen to me before, systemd being too quick thus trigger this
kind of races.

I mean, could this be like this?:
 * systemd loads de module and returns (without waiting for the module
loading to return)
 * systemd then loads the sysctl. The module is loading, sysctl are
not yet there.

>
> To me this smells like a kernel problem, specifically the conntrack
> module and should be addressed there. But this would need input from a
> kernel maintainer.
>

I'm not sure if the problem is the module.
The module just creates the sysctl entries at module loading time
and that's all [0].

Don't know if another approach could be used by the module.

[0] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/net/netfilter/nf_conntrack_standalone.c#n639