d841064777
Userspace apps are supposed to release all ib device resources if they receive a fatal async event (IBV_EVENT_DEVICE_FATAL). However, the app has no way of knowing when the device has come back up, except to repeatedly attempt ibv_open_device() until it succeeds. However, currently there is no protection against the open succeeding while the device is in being removed following the fatal event. In this case, the open will succeed, but as a result the device waits in the middle of its removal until the new app releases its resources -- and the new app will not do so, since the open succeeded at a point following the fatal event generation. This patch adds an "active" flag to the device. The active flag is set to false (in the fatal event flow) before the "fatal" event is generated, so any subsequent ibv_dev_open() call to the device will fail until the device comes back up, thus preventing the above deadlock. Signed-off-by: Jack Morgenstein <jackm@dev.mellanox.co.il> Signed-off-by: Roland Dreier <rolandd@cisco.com> |
||
|---|---|---|
| .. | ||
| Kconfig | ||
| Makefile | ||
| mthca_allocator.c | ||
| mthca_av.c | ||
| mthca_catas.c | ||
| mthca_cmd.c | ||
| mthca_cmd.h | ||
| mthca_config_reg.h | ||
| mthca_cq.c | ||
| mthca_dev.h | ||
| mthca_doorbell.h | ||
| mthca_eq.c | ||
| mthca_mad.c | ||
| mthca_main.c | ||
| mthca_mcg.c | ||
| mthca_memfree.c | ||
| mthca_memfree.h | ||
| mthca_mr.c | ||
| mthca_pd.c | ||
| mthca_profile.c | ||
| mthca_profile.h | ||
| mthca_provider.c | ||
| mthca_provider.h | ||
| mthca_qp.c | ||
| mthca_reset.c | ||
| mthca_srq.c | ||
| mthca_uar.c | ||
| mthca_user.h | ||
| mthca_wqe.h | ||