Ishai Rabinovitz wrote: > There is a bug in SRP Engenio target that send a large value as service > timeout. (It gets 30 which mean timeout of (2^(30-8))=4195 sec.) Such a long > timeout is not reasonable and it may leave the kernel module waiting on > wait_for_completion and may stuck a lot of processes. > > The following patch allows the load of ib_cm module with a limit on the > timeout.
There's several timeout values transfered and used by the cm, most notably the remote cm response timeout and packet life time. Does it make more sense to have a single, generic timeout maximum instead? Would it make more sense to enable the maximum(s) by default, since we're dependent upon values received over the network? - Sean _______________________________________________ openib-general mailing list [email protected] http://openib.org/mailman/listinfo/openib-general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
