If the interface address referenced by a cloning route did not point to an interface any more, the kernel crashed with a null pointer dereference.  This situation could be created by a strange sequence of route and ifconfig commands. Now when a cloning route references a stale interface address and rtrequest1(RTM_RESOLVE) has to create a cloned route, it does a lookup for a valid interface address with the same ip address.  The new interface address and its interface are used for the new cloned route and they replace the old ones at the cloning route. ok claudio@, henning@
If the interface address referenced by a cloning route did not point
to an interface any more, the kernel crashed with a null pointer
dereference.  This situation could be created by a strange sequence
of route and ifconfig commands.
Now when a cloning route references a stale interface address and
rtrequest1(RTM_RESOLVE) has to create a cloned route, it does a
lookup for a valid interface address with the same ip address.  The
new interface address and its interface are used for the new cloned
route and they replace the old ones at the cloning route.
ok claudio@, henning@

orumin/openbsd-efivars,orumin/openbsd-efivars,orumin/openbsd-efivars,orumin/openbsd-efivars