From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Gao Feng <gfree.wind@foxmail.com>
Cc: netfilter-devel@vger.kernel.org, 'Gao Feng' <fgao@ikuai8.com>
Subject: Re: [PATCH nf-next v2 1/1] netfilter: helper: Remove useless rcu lock when get expectfn
Date: Wed, 29 Mar 2017 12:44:12 +0200 [thread overview]
Message-ID: <20170329104412.GA6337@salvia> (raw)
In-Reply-To: <000301d2a877$4e174c50$ea45e4f0$@foxmail.com>
On Wed, Mar 29, 2017 at 06:29:10PM +0800, Gao Feng wrote:
> Hi Pablo,
>
> > -----Original Message-----
> > From: Pablo Neira Ayuso [mailto:pablo@netfilter.org]
> > Sent: Wednesday, March 29, 2017 6:08 PM
> > To: gfree.wind@foxmail.com
> > Cc: netfilter-devel@vger.kernel.org; Gao Feng <fgao@ikuai8.com>
> > Subject: Re: [PATCH nf-next v2 1/1] netfilter: helper: Remove useless rcu
> lock
> > when get expectfn
> >
> > On Wed, Mar 22, 2017 at 10:15:02AM +0800, gfree.wind@foxmail.com wrote:
> > > From: Gao Feng <fgao@ikuai8.com>
> > >
> > > Because these two functions return the nf_ct_helper_expectfn pointer
> > > which should be protected by rcu lock. So it should makes sure the
> > > caller should hold the rcu lock, not inside these functions.
> > >
> > > Signed-off-by: Gao Feng <fgao@ikuai8.com>
> > > ---
> > > v2: Shorter subject, per Pablo
> > > v1: Initial version
> > >
> > > net/netfilter/nf_conntrack_helper.c | 6 ++----
> > > 1 file changed, 2 insertions(+), 4 deletions(-)
> > >
> > > diff --git a/net/netfilter/nf_conntrack_helper.c
> > > b/net/netfilter/nf_conntrack_helper.c
> > > index 6dc44d9..bce3d1f 100644
> > > --- a/net/netfilter/nf_conntrack_helper.c
> > > +++ b/net/netfilter/nf_conntrack_helper.c
> > > @@ -311,38 +311,36 @@ void nf_ct_helper_expectfn_unregister(struct
> > > nf_ct_helper_expectfn *n) }
> > > EXPORT_SYMBOL_GPL(nf_ct_helper_expectfn_unregister);
> > >
> > > +/* Caller should hold the rcu lock */
> > > struct nf_ct_helper_expectfn *
> > > nf_ct_helper_expectfn_find_by_name(const char *name) {
> > > struct nf_ct_helper_expectfn *cur;
> > > bool found = false;
> > >
> > > - rcu_read_lock();
> > > list_for_each_entry_rcu(cur, &nf_ct_helper_expectfn_list, head) {
> > > if (!strcmp(cur->name, name)) {
> > > found = true;
> > > break;
> > > }
> > > }
> > > - rcu_read_unlock();
> > > return found ? cur : NULL;
> > > }
> > > EXPORT_SYMBOL_GPL(nf_ct_helper_expectfn_find_by_name);
> >
> > nf_ct_helper_expectfn_find_by_name() is called from ctnetlink, via
> > ctnetlink_create_expect() and rcu read side lock is not held there.
> There are two reasons.
> 1. The rcu lock would be added in my patch " netfilter: helper: Add the rcu
> lock when call __nf_conntrack_helper_find" for nf
> https://patchwork.ozlabs.org/patch/741865/.
If you have interdependencies between two patches like this, it's
better to make it in one single go.
> So the ctnetlink_create_expect would hold the rcu lock after apply that
> patch.
>
> 2. Because these two functions return one pointer which needs RCU lock, so
> the caller must hold rcu lock.
> Or it still meets one error even though there is one rcu lock in these two
> functions.
> Because the memory which the returned pointer point to would be freed
> already after rcu_read_unlock.
> So the rcu lock is unnecessary in these functions.
That's right. You're fixing up a real problem, no doubt.
I'm just questioning that I think that if you are fixing up rcu
locking, which seems to be the case, you just do it in one single
patch.
Thanks!
next prev parent reply other threads:[~2017-03-29 10:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-22 2:15 [PATCH nf-next v2 1/1] netfilter: helper: Remove useless rcu lock when get expectfn gfree.wind
2017-03-29 10:07 ` Pablo Neira Ayuso
2017-03-29 10:29 ` Gao Feng
2017-03-29 10:44 ` Pablo Neira Ayuso [this message]
2017-03-29 10:50 ` Gao Feng
2017-03-29 11:49 ` Pablo Neira Ayuso
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=20170329104412.GA6337@salvia \
--to=pablo@netfilter.org \
--cc=fgao@ikuai8.com \
--cc=gfree.wind@foxmail.com \
--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).