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 nft] src: delete the old cache when dumping is interrupted
Date: Wed, 17 May 2017 20:14:07 +0200 [thread overview]
Message-ID: <20170517181407.GA15476@salvia> (raw)
In-Reply-To: <20170514075612.29226-1-zlpnobody@163.com>
On Sun, May 14, 2017 at 03:56:12PM +0800, Liping Zhang wrote:
> From: Liping Zhang <zlpnobody@gmail.com>
>
> When the dumping operation is interrupted, we will restart the
> cache_init(), but unfortunatly, we forget to delete the old cache.
> So in extreme case, we will leak a huge amount of memory.
>
> Running the following commands can simulate the extreme case:
> # nft add table t
> # nft add set t s {type inet_service \;}
> # for i in $(seq 65000); do
> nft add element t s {$i}
> done &
> # while : ; do
> time nft list ruleset -nn
> done
>
> After a while, oom killer will be triggered:
> [ 2808.243537] Out of memory: Kill process 16975 (nft) score 649 or
> sacrifice child
> [ 2808.255372] Killed process 16975 (nft) total-vm:1955348kB,
> anon-rss:1952120kB, file-rss:0kB, shmem-rss:0kB
> [ 2858.353729] nft invoked oom-killer: gfp_mask=0x14201ca(GFP_HIGHUSER_
> MOVABLE|__GFP_COLD), nodemask=(null), order=0,
> oom_score_adj=0
> [ 2858.374521] nft cpuset=/ mems_allowed=0
> ...
Applied, thanks.
prev parent reply other threads:[~2017-05-17 18:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-14 7:56 [PATCH nft] src: delete the old cache when dumping is interrupted Liping Zhang
2017-05-17 18:14 ` 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=20170517181407.GA15476@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).