| Using a DCCP_ prefix for BUG(), BUG_ON(), WARN_ON() and a new WARN() | with the difference being none would panic the machine, but warn, in | some cases ratelimited, seems to be the way to go, later, as you | suggests, we just remove the prefix. I will take this into consideration and work on that until tomorrow. | > For the moment, as Ian has pointed out, bringing the machine to a grinding halt for every little | > problem is probably too much of a nuisance (in the same vein, I would really like to suggest the | > return of Unload Hack :0). | | I'll look at what to do to avoid allowing the removal while there are | TW sockets on the death row :-) I had meant to look into what David said about socket references, but my knowledge of module internals is probably not so great (but intended to catch up on this). Currently all modules have to be ejected in some order (ccids -> dccp_ipv6 -> dccp_ipv4 -> dccp); I attach the script which I am using for unloading, this doesn't solve the Unload Hack, but has been useful. Gerrit
Attachment:
dccp_module_unload_script.pl
Description: Perl program
