| Hence I think we have a chance by going completely lockless here, by | loading all configured CCIDs at runtime. In this manner the per-connection | check "are all advertised CCIDs are loaded?" falls under the table, we | do not need to worry about concurrent access, and loading DCCP implies that | all needed CCIDs are there. Unfortunately this won't work since the CCIDs depend on dccp.ko being fully loaded, so requiring that CCID module are loaded during the loading process of dccp.ko creates a cyclic dependency. -- To unsubscribe from this list: send the line "unsubscribe dccp" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
