Subject: Re: kern/29531: Active FTP support with NAT causes panic
To: None <kern-bug-people@netbsd.org, gnats-admin@netbsd.org,>
From: Pavel Cahyna <pavel.cahyna@st.cuni.cz>
List: netbsd-bugs
Date: 02/26/2005 17:47:02
The following reply was made to PR kern/29531; it has been noted by GNATS.

From: Pavel Cahyna <pavel.cahyna@st.cuni.cz>
To: gnats-bugs@netbsd.org
Cc: 
Subject: Re: kern/29531: Active FTP support with NAT causes panic
Date: Sat, 26 Feb 2005 18:46:16 +0100

 On Sat, 26 Feb 2005 05:15:00 +0000, apz-list wrote:
 
 >         I was transferring files with a Windows' WS_FTP, as the FTP
 connection
 >         froze. I reconnected and resumed the transfer, but after a
 >         minute or so it froze again and the NAT box had paniced.
 >         
 >         Here's the output from trace: http://apz.fi/tmp/trace.jpg
 
 I am also seeing this on a 2.0_BETA machine:
 
 panic: m_copydata
 cpu_Debugger(c0a82cc0,c0c9c154,c0e65e00,28,0) at netbsd:cpu_Debugger+0x4
 panic(c0691d6e,c0c9c1cc,28,28,33) at netbsd:panic+0x11d
 m_cat(c0c9c100,78,2b,c0d1d310,c0c9c100) at netbsd:m_cat
 ippr_ftp_process(c0a82cc0,c0e65e00,c0d1d200,1,c0c9c100) at netbsd:ippr_ftp_process+0x1ce
 ippr_ftp_in(c0a82cc0,c0c9eb80,c0e65e00,0,c0bb2200) at netbsd:ippr_ftp_in+0x4e
 appr_check(c0a82cc0,c0e65e00,15006804,c0a82cbc,c0a82cc0) at netbsd:appr_check+0x152
 fr_natin(c0a82cc0,c0e65e00,1,1,14) at netbsd:fr_natin+0x166
 fr_checknatin(c0a82cc0,c0a82cbc,c0a82cc0,28,0) at netbsd:fr_checknatin+0xca
 fr_check(c0c9c154,14,c0b81034,0,c0a82dd8) at netbsd:fr_check+0x53a
 fr_check_wrapper(0,c0a82dd8,c0b81034,1,c0c9c100) at netbsd:fr_check_wrapper+0x56
 pfil_run_hooks(c0767900,c0a82e40,c0b81034,1,4) at netbsd:pfil_run_hooks+0x5b
 ip_input(c0c9c100,c04e6435,c0a82e6c,1,0) at netbsd:ip_input+0x8af
 ipintr(ddf50010,30,5f10010,10,c0a7f000) at netbsd:ipintr+0xfa
 DDB lost frame for netbsd:Xsoftnet+0x40, trying 0xc0a82e70
 Xsoftnet() at netbsd:Xsoftnet+0x40
 --- interrupt ---
 0x246:
 
 Not all IPFilter updates are applied, though. Specifically, ticket #833
 was not applied. But since this happens on release too, it is probably not
 relevant. I disabled the ftp-proxy and told people to use active FTP as a
 workaround.