Skip to content
  • Eric W. Biederman's avatar
    net: Guaranetee the proper ordering of the loopback device. v2 · 505d4f73
    Eric W. Biederman authored
    
    
    I was recently hunting a bug that occurred in network namespace
    cleanup.  In looking at the code it became apparrent that we have
    and will continue to have cases where if we have anything going
    on in a network namespace there will be assumptions that the
    loopback device is present.   Things like sending igmp unsubscribe
    messages when we bring down network devices invokes the routing
    code which assumes that at least the loopback driver is present.
    
    Therefore to avoid magic initcall ordering hackery that is hard
    to follow and hard to get right insert a call to register the
    loopback device directly from net_dev_init().    This guarantes
    that the loopback device is the first device registered and
    the last network device to go away.
    
    But do it carefully so we register the loopback device after
    we clear dev_boot_phase.
    
    Signed-off-by: default avatarEric W. Biederman <ebiederm@maxwell.aristanetworks.com>
    Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
    505d4f73