From: 董董侃 <doublefacer007@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: kernel BUG in ip_nat_helper_unregister at netfilter/ip_nat_helper.c
Date: Sun, 3 Sep 2006 22:16:05 +0800 [thread overview]
Message-ID: <ccbc91640609030716o221dad8as9278b2081a28c490@mail.gmail.com> (raw)
Hi,
I has found a bug that is caused by dead lock on ip_nat_ftp module
in linux kernel 2.4.27 on SMP machine.My workaround of testing is as following:
I create a router by iptables ,FTP client and FTP server for testing.
client machine ip: 192.168.1.3/32 ,gateway 192.168.1.10/32
server machine ip: 192.168.2.3/32,gateway 192.168.2.10/32
router machine with tow NICs,
eth0:192.168.1.10/32
eth1:192.168.2.10/32
Testing flow:
on router:
echo 1 > /proc/sys/net/ipv4/ip_forward
modprobe ip_nat_ftp
iptables -t nat -A POSTROUTING -s 192.168.1.3 -p tcp --dport 21
-o eth1 -j SNAT --to-source 192.168.2.10
on client:
I use a benchmark tool to create ftp sessions with the remote
FTP server.In the session,includes ftp control connections and data
connections.The sending rate is about 500 sessions/10s.
When the num of conntrack is up to 15000,I rmmod the ip_nat_ftp
and ip_conntrack _ftp modules by typing "modprobe -r ip_nat_ftp"
command and then the kernel is dead locked.
I think that the dead lock is caused by ip_conntrack_lock and
ip_nat_lock.When I rmmod the ip_nat_ftp module, the function flow is
as following:
ip_nat_helper_unregister->ip_ct_selective_cleanup->get_next_corpse(ip_conntrack_lock)
->kill_helper(ip_nat_lock)
But the kernel there is another flow is as following:
ip_nat_fn(ip_nat_lock)->ip_nat_setup_info->ip_conntrack_alter_reply(ip_conntrack_lock)
--
VGER BF report: U 0.502111
next reply other threads:[~2006-09-03 14:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-03 14:16 董董侃 [this message]
2006-09-03 14:46 ` Patrick McHardy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ccbc91640609030716o221dad8as9278b2081a28c490@mail.gmail.com \
--to=doublefacer007@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®