diff options
author | Jack Morgenstein <jackm@dev.mellanox.co.il> | 2008-02-13 16:23:50 +0200 |
---|---|---|
committer | Roland Dreier <rolandd@cisco.com> | 2008-02-14 10:15:06 -0800 |
commit | 167c42655cca188657aa9bb4e06d1194af3c73a5 (patch) | |
tree | 52e500e426a6d4a77acdc68333c6dcae0bc342c8 /mm/fadvise.c | |
parent | 5163dc1a645bc9ed7984fa484f1a77378c166d23 (diff) |
IPoIB: On P_Key change event, reset state properly
In P_Key event handling, if the old P_Key is no longer available, the
driver must call ipoib_ib_dev_stop() -- just as it does when the P_Key
is still available (see procedure __ipoib_ib_dev_flush()).
When a P_Key becomes available, the driver will perform ipoib_open(),
which assumes that the QP is in RESET, the cm_id has been
destroyed/deleted, etc. If ipoib_ib_dev_stop() is not called as
described above, then these assumptions will be false, and the attempt
to bring the interface up will fail.
Found by Mellanox QA.
Signed-off-by: Jack Morgenstein <jackm@dev.mellanox.co.il>
Signed-off-by: Roland Dreier <rolandd@cisco.com>
Diffstat (limited to 'mm/fadvise.c')
0 files changed, 0 insertions, 0 deletions