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

[Michael Biebl]

Am 13.07.2017 um 12:55 schrieb 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)

Not afaics. systemd-modules-load.service uses Type=oneshot, i.e. it
waits until /lib/systemd/systemd-modules-load has finished before it
proceeds with starting systemd-sysctl.service.

systemd-modules-load uses libkmod/kmod_module_probe_insert_module() to
load the modules:
https://github.com/systemd/systemd/blob/master/src/modules-load/modules-load.c


I.e. it's not doing something fancy here and uses the same functionality
as modprobe/insmod does.

Can we expect that the sysfs entries are available after loading the
conntrack module?

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20170713/38eb640a/attachment-0002.sig>