From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Liping Zhang <zlpnobody@gmail.com>
Cc: Liping Zhang <zlpnobody@163.com>,
Netfilter Developer Mailing List
<netfilter-devel@vger.kernel.org>
Subject: Re: [PATCH nf V2] netfilter: nf_ct_helper: permit cthelpers with different names via nfnetlink
Date: Sat, 15 Apr 2017 11:28:20 +0200 [thread overview]
Message-ID: <20170415092820.GA5125@salvia> (raw)
In-Reply-To: <20170413235702.GA10583@salvia>
On Fri, Apr 14, 2017 at 01:57:02AM +0200, Pablo Neira Ayuso wrote:
> On Fri, Apr 14, 2017 at 07:50:26AM +0800, Liping Zhang wrote:
> > Hi Pablo,
> >
> > 2017-04-14 6:29 GMT+08:00 Pablo Neira Ayuso <pablo@netfilter.org>:
> > [...]
> > >> After I have a closer look, inside hlist_for_each_entry_rcu, we use the
> > >> rcu_dereference_raw() to get the pointer, and this will not generate warning:
> > >>
> > >> #define hlist_for_each_entry_rcu(pos, head, member) \
> > >> for (pos = hlist_entry_safe (rcu_dereference_raw(hlist_first_rcu(head)),\
> > >> typeof(*(pos)), member);
> > >> ....
> > >>
> > >> Then "This is likely going to spot false positives with the RCU
> > >> debugging instrumentation"
> > >> will not happen.
> > >
> > > Right, instrumentation will not trigger any problem.
> > >
> > > But even if instrumention is not a problem, I just would like to avoid
> > > people sending me "obvious" fixes afterwards, by removing _rcu since
> > > they see this code runs under mutex or how knows what.
> >
> > I'm a little confusing about this one.
> >
> > I found "http://patchwork.ozlabs.org/patch/744786/" and
> > "http://patchwork.ozlabs.org/patch/743472/" were both set
> > to "Changes Requested".
> >
> > So which one is you prefer to :)? What's next step should I do?
>
> The latter, please resubmit bumping your version number and log.
>
> That makes things easier for me than going back and forth trying to
> figure out what I should do, thanks!
Hm, this patch requires no changes actually. Now I understand why
you're confused there.
So let me know if you I should just take this or wait for you to
resubmit.
In case of doubt, resubmitting is just fine. Thanks!
next prev parent reply other threads:[~2017-04-15 9:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-29 13:00 [PATCH nf V2] netfilter: nf_ct_helper: permit cthelpers with different names via nfnetlink Liping Zhang
2017-03-30 2:12 ` Liping Zhang
2017-04-13 22:29 ` Pablo Neira Ayuso
2017-04-13 23:50 ` Liping Zhang
2017-04-13 23:57 ` Pablo Neira Ayuso
2017-04-15 9:28 ` Pablo Neira Ayuso [this message]
2017-04-15 9:34 ` Liping Zhang
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=20170415092820.GA5125@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).