Otherwise this can lead to the BUG_TRAP in __xfrm_state_destroy when
xfrm_state_put() finds this is the last reference.

- the found or allocated xfrm_states are not passed correctly to
  xfrm_bundle_create (and to the subsequent frees in case of create
  failing) if the first xfrm_tmpl_resolve failed and the second one
  succeeded.
- error handling is wrong.

Otherwise we can trigger the BUG trap in __xfrm_state_destroy() when
xfrm_state_put() finds this is the last reference.

Remove duplicate/conflicting code
now that netdev_register_notifier replays the device registration events.

Remove duplicate/conflicting code now that netdev_register_notifier replays the
device registration events. Reorder initialization to avoid having to simplify error unwind
if /proc creation failed.

Remove duplicate/conflicting code 
now that netdev_register_notifier replays the device registration events.

Change IPV6 to handle the new case where netdev events are replayed on registration:
* change code ordering so address configuration is ready before registration
  (this was actually a bug in existing code)
* take out code that capture's existing devices, this is now done in the replay
* make notifier code local to addrconf.c so it can be have smaller scope

into home.osdl.org:/home/torvalds/v2.5/linux

Spotted by Matteo Croce 

into home.osdl.org:/home/torvalds/v2.5/linux

From Martin Diehl.

From Martin Diehl.

Also, make sir-dev locking compatible with irport.
From Martin Diehl.

[ATM]: br2684 incorrectly handles frames recvd with FCS (by Alex Zeffertt <ajz@cambridgebroadband.com>)