Revision be4b499323bf7291b491c6df51baae62f45b8404 authored by Erez Shitrit on 25 June 2015, 14:13:22 UTC, committed by Doug Ledford on 14 July 2015, 17:20:09 UTC
Whenever ib_cm gets remove_one call, like when there is a hot-unplug event, the driver should mark itself as going_down and confirm that no new works are going to be queued for that device. so, the order of the actions are: 1. mark the going_down bit. 2. flush the wq. 3. [make sure no new works for that device.] 4. unregister mad agent. otherwise, works that are already queued can be scheduled after the mad agent was freed. Signed-off-by: Erez Shitrit <erezsh@mellanox.com> Signed-off-by: Doug Ledford <dledford@redhat.com>
1 parent 3fdf70a
File | Mode | Size |
---|---|---|
00-INDEX | -rw-r--r-- | 1.5 KB |
CREDITS | -rw-r--r-- | 1.9 KB |
HiSax.cert | -rw-r--r-- | 3.9 KB |
INTERFACE | -rw-r--r-- | 27.2 KB |
INTERFACE.CAPI | -rw-r--r-- | 14.1 KB |
INTERFACE.fax | -rw-r--r-- | 4.5 KB |
README | -rw-r--r-- | 28.6 KB |
README.FAQ | -rw-r--r-- | 721 bytes |
README.HiSax | -rw-r--r-- | 23.3 KB |
README.act2000 | -rw-r--r-- | 3.5 KB |
README.audio | -rw-r--r-- | 5.8 KB |
README.avmb1 | -rw-r--r-- | 5.5 KB |
README.concap | -rw-r--r-- | 10.5 KB |
README.diversion | -rw-r--r-- | 6.1 KB |
README.fax | -rw-r--r-- | 1.1 KB |
README.gigaset | -rw-r--r-- | 17.5 KB |
README.hfc-pci | -rw-r--r-- | 1.8 KB |
README.hysdn | -rw-r--r-- | 7.8 KB |
README.icn | -rw-r--r-- | 5.0 KB |
README.mISDN | -rw-r--r-- | 328 bytes |
README.pcbit | -rw-r--r-- | 1.6 KB |
README.sc | -rw-r--r-- | 11.9 KB |
README.syncppp | -rw-r--r-- | 2.1 KB |
README.x25 | -rw-r--r-- | 7.1 KB |
syncPPP.FAQ | -rw-r--r-- | 7.9 KB |
![swh spinner](/static/img/swh-spinner.gif)
Computing file changes ...