I am getting kernel panics due to a NULL dereference in sctp_getsockopt_sctp_status() when calling getsockopt() with SCTP_STATUS immediately after establishing a connection. This occurs when transport = asoc->peer.primary_path; is NULL and transport is later dereferenced. Is there any way that an association would be present but have no primary_path? Should sctp_getsockopt_sctp_status() be checking asoc->peer.primary_path and returning -EINVAL? Karl -- To unsubscribe from this list: send the line "unsubscribe linux-sctp" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
