This problem was the bug of packet_set_ring(). packet_set_ring()
removes the hook for preparation of ring buffer, but it didn't
restore.

Also it's leaking the refcount of sk.

into nuts.ninka.net:/disk1/davem/BK/net-2.6

into redhat.com:/spare/repo/net-drivers-2.5

Decnet exposes itself to proc and packets before it has finished initializing.
This was always a race, but the notifier replay might expose it worse.

Patch from Russell King.

into redhat.com:/spare/repo/net-drivers-2.5

into redhat.com:/spare/repo/net-drivers-2.5

into redhat.com:/spare/repo/net-drivers-2.5

into redhat.com:/spare/repo/net-drivers-2.5

  This was broken by the last commit for cdev stuff which removed the
  "int ret;" that these routines used.

  Retire our char device dispatching logic.  With the 2.6 cdev API we
  can register much smaller device number regions, so we use that instead.

into nuts.ninka.net:/disk1/davem/BK/net-2.6

This patch updates the CREDITS and MAINTAINERS files to reflect the change
of the maintainer role for the Bluetooth subsystem.

If the inquiry cache is empty it makes no sense to return zero number of
inquiry result even if the age of cache is not outdated.

The L2CAP reference counting must be increased by the RFCOMM module if an
incoming connection is accepted. If this is not done, it will be decreased
one time to often if the connection is terminated.

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.