Description of problem:
When stopping iptables with ip_nat_ftp loaded and there are ftp connections, 
the session stopping 

[root@shopping root]# service iptables start
Applying iptables firewall rules:                          [  OK  ]
Loading additional iptables modules: ip_nat_ftp            [  OK  ]
[root@shopping root]# service iptables stop
Flushing firewall rules:                                   [  OK  ]
Setting chains to policy ACCEPT: filter nat                [  OK  ]
Unloading iptables modules:

Session hangs here, server still accessable with 1 CPU pegged at 99.9%

[root@shopping root]# ps -ef | grep modprobe
root      2310  2240 99 10:40 pts/0    00:02:06 modprobe -r ip_nat_ftp
root      2415  2327  0 10:42 pts/2    00:00:00 grep modprobe
[root@shopping root]# kill 2240
[root@shopping root]# ps -ef | grep modprobe
root      2310     1 99 10:40 pts/0    00:02:57 modprobe -r ip_nat_ftp
root      2429  2327  0 10:43 pts/2    00:00:00 grep modprobe
[root@shopping root]# kill -s 9 2310
[root@shopping root]# kill -9 2310
[root@shopping root]# ps -ef | grep modprobe
root      2310     1 99 10:40 pts/0    00:03:17 modprobe -r ip_nat_ftp
root      2431  2327  0 10:43 pts/2    00:00:00 grep modprobe

Process 2310 seems unkillable.  Reboot required to get rid of it


Version-Release number of selected component (if applicable):
[root@shopping root]# rpm -qa | grep modutil
modutils-2.4.18-3.7x
[root@shopping root]# rpm -qa | grep kern
kernel-smp-2.4.20-20.7
[root@shopping root]# rpm -qa | grep iptables
iptables-1.2.8-8.72.3


How reproducible:
Every time.

Steps to Reproduce:
1.Load/Start iptables with ip_nat_ftp as an extra module
2.Make an FTP connection
3.Unload/Stop iptables

    
Actual results:
I was left with an unkillable process taking all the CPU.

Expected results:
I would not be left with an unkillable process taking all the CPU.  ip_nat_ftp 
would unload.

Additional info: