On Tue, Apr 14, 2015 at 01:43:11PM -0400, ira.weiny wrote: > A failure to init port 2 ends up ends up "killing" port 1 and releasing the > device associated resources.
Yes, that is the only reasonable thing that could happen. init failure should only be possible under exceptional cases (OOM). The only system response is to call ib_umad_add_one again - so of course the first call had to completely clean up everything it did. Hopefully all these errors propogate enough so that driver insmod fails with a perfect clean up. Otherwise it is broken :| Jason -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
