Bug#899002: systemd: networking and rdma-load-modules at infiniband service run in parallel despite the declared dependency order

Michael Biebl biebl at debian.org
Fri May 18 20:23:32 BST 2018


Am 18.05.2018 um 19:22 schrieb Benjamin Drung:
> Am Freitag, den 18.05.2018, 13:14 -0400 schrieb Felipe Sateler:
>> Control: tags -1 moreinfo
>> On Fri, May 18, 2018 at 8:57 AM Benjamin Drung <benjamin.drung at profit
>> bricks.com> wrote:

>>> $ systemctl cat rdma-load-modules at infiniband.service
>>> # /lib/systemd/system/rdma-load-modules at .service

>>> Before=sysinit.target


>>> Before=network-pre.target


>>> # Orders all kernel module startup before rdma-hw.target can become
>>> # ready
>>> Before=rdma-hw.target

All those Before orderings can not be guaranteed, if
rdma-load-modules at .service is started via a udev rule (dynamically).

udev can trigger the start of that service at any time during boot when
those targets are already active and systemd can't know that it has to
wait for rdma-load-modules at infiniband.service as it doesn't have that
information when it computes the initial boot transaction.

So this is really a problem of how rdma-load-modules at .service and
rdma-hw.target are implemented. They are not going to work like you
expected it to work, i.e. having a rdma-hw.target which other units can
order itself against reliably.


-- 
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/20180518/827a0154/attachment-0002.sig>


More information about the Pkg-systemd-maintainers mailing list