Re: Where did vm_operations_struct->unmap in 2.4.0 go?

[Alan Cox]

> Stick to one method that works for all routines, dynamic registration.
> If that imposes the occasional need for a couple of extra calls in some
> routines and for people to think about initialisation order right from
> the start then so be it, it is a small price to pay for long term
> stability and ease of maintenance.

What happens when we get a loop in init order because of binding and other init
order conflicts?