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-- | 170 bytes |
| client.txt | -rw-r--r-- | 7.6 KB |
| dmatest.txt | -rw-r--r-- | 3.4 KB |
| provider.txt | -rw-r--r-- | 15.4 KB |
| pxa_dma.txt | -rw-r--r-- | 7.1 KB |
Computing file changes ...
