From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Liping Zhang <zlpnobody@163.com>
Cc: netfilter-devel@vger.kernel.org, Liping Zhang <zlpnobody@gmail.com>
Subject: Re: [PATCH nf] netfilter: ctnetlink: fix incorrect nf_ct_put during hash resize
Date: Wed, 24 May 2017 12:24:44 +0200 [thread overview]
Message-ID: <20170524102444.GA23086@salvia> (raw)
In-Reply-To: <1495322569-63361-1-git-send-email-zlpnobody@163.com>
On Sun, May 21, 2017 at 07:22:49AM +0800, Liping Zhang wrote:
> From: Liping Zhang <zlpnobody@gmail.com>
>
> If nf_conntrack_htable_size was adjusted by the user during the ct
> dump operation, we may invoke nf_ct_put twice for the same ct, i.e.
> the "last" ct. This will cause the ct will be freed but still linked
> in hash buckets.
>
> It's very easy to reproduce the problem by the following commands:
> # while : ; do
> echo $RANDOM > /proc/sys/net/netfilter/nf_conntrack_buckets
> done
> # while : ; do
> conntrack -L
> done
> # iperf -s 127.0.0.1 &
> # iperf -c 127.0.0.1 -P 60 -t 36000
>
> After a while, the system will hang like this:
> NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [bash:20184]
> NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [iperf:20382]
> ...
>
> So at last if we find cb->args[1] is equal to "last", this means hash
> resize happened, then we can set cb->args[1] to 0 to fix the above
> issue.
Applied, thanks.
I have added:
Fixes: d205dc40798d ("[NETFILTER]: ctnetlink: fix deadlock in table dumping")
prev parent reply other threads:[~2017-05-24 10:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-20 23:22 [PATCH nf] netfilter: ctnetlink: fix incorrect nf_ct_put during hash resize Liping Zhang
2017-05-21 0:00 ` Florian Westphal
2017-05-21 0:59 ` Liping Zhang
2017-05-23 21:34 ` Pablo Neira Ayuso
2017-05-23 22:28 ` Florian Westphal
2017-05-24 0:52 ` Liping Zhang
2017-05-24 6:22 ` Florian Westphal
2017-05-24 10:24 ` Pablo Neira Ayuso [this message]
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=20170524102444.GA23086@salvia \
--to=pablo@netfilter.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=zlpnobody@163.com \
--cc=zlpnobody@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).