From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Vasily Averin <vvs@virtuozzo.com>
Cc: netfilter-devel@vger.kernel.org,
Jozsef Kadlecsik <kadlec@netfilter.org>,
Florian Westphal <fw@strlen.de>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH v2] ipset: enable memory accounting for ipset allocations
Date: Sun, 4 Oct 2020 21:09:13 +0200 [thread overview]
Message-ID: <20201004190913.GA3788@salvia> (raw)
In-Reply-To: <343416af-f22f-3834-7ee9-14b6dd7558ff@virtuozzo.com>
On Fri, Sep 25, 2020 at 11:56:02AM +0300, Vasily Averin wrote:
> Currently netadmin inside non-trusted container can quickly allocate
> whole node's memory via request of huge ipset hashtable.
> Other ipset-related memory allocations should be restricted too.
Applied, thanks.
next prev parent reply other threads:[~2020-10-04 19:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-25 5:55 [PATCH] ipset: enable memory accounting for ipset allocations Vasily Averin
2020-09-25 7:53 ` kernel test robot
2020-09-25 8:56 ` [PATCH v2] " Vasily Averin
2020-10-04 19:09 ` Pablo Neira Ayuso [this message]
2020-09-25 9:13 ` [PATCH] " kernel test robot
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=20201004190913.GA3788@salvia \
--to=pablo@netfilter.org \
--cc=davem@davemloft.net \
--cc=fw@strlen.de \
--cc=kadlec@netfilter.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=vvs@virtuozzo.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).