From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: Florian Westphal <fw@strlen.de>, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH ipset nf-next] netfilter: ipset: add resched points during set listing
Date: Wed, 6 Dec 2017 09:18:48 +0100 [thread overview]
Message-ID: <20171206081848.GB4027@salvia> (raw)
In-Reply-To: <alpine.DEB.2.11.1712012018190.26668@blackhole.kfki.hu>
On Fri, Dec 01, 2017 at 08:25:55PM +0100, Jozsef Kadlecsik wrote:
> Hi Florian,
>
> On Thu, 30 Nov 2017, Florian Westphal wrote:
>
> > When sets are extremely large we can get softlockup during ipset -L. We
> > could fix this by adding cond_resched_rcu() at the right location during
> > iteration, but this only works if RCU nesting depth is 1.
> >
> > At this time entire variant->list() is called under under
> > rcu_read_lock_bh. This used to be a read_lock_bh() but as rcu doesn't
> > really lock anything, it does not appear to be needed, so remove it
> > (ipset increments set reference count before this, so a set deletion
> > should not be possible).
>
> Yes, the call of rcu_read_lock_bh() seems to be unnecessary, the
> set->variant->list() functions protect the sensitive parts with
> rcu_read_lock() anyway. Thanks!
>
> Acked-by: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Also applied, thanks.
prev parent reply other threads:[~2017-12-06 8:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-30 20:08 [PATCH ipset nf-next] netfilter: ipset: add resched points during set listing Florian Westphal
2017-12-01 19:25 ` Jozsef Kadlecsik
2017-12-06 8:18 ` 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=20171206081848.GB4027@salvia \
--to=pablo@netfilter.org \
--cc=fw@strlen.de \
--cc=kadlec@blackhole.kfki.hu \
--cc=netfilter-devel@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;
as well as URLs for NNTP newsgroup(s).