On 01/21/10 12:34 AM, Peter Memishian wrote:

  >  Lots of drivers call mac_unregister(), and *then* disable callbacks,
  >  interrupts, etc.
  >
  >  This makes sense, because you don't want to tear all that stuff down if
  >  the mac is going to refuse to detach because its busy.

This is why Seb introduced mac_disable() a while back.  Once mac_disable()
succeeds, you can be certain mac_unregister() will not fail.

Indeed. The remaining work would be to make use of it in drivers that contain those potential races.

-Seb
_______________________________________________
networking-discuss mailing list
[email protected]

Reply via email to