From: Sabrina Dubroca <sd@queasysnail.net>
To: Fan Du <fan.du@windriver.com>
Cc: steffen.klassert@secunet.com, davem@davemloft.net,
netdev@vger.kernel.org
Subject: Re: [PATCHv2 net-next 3/4] flowcache: Fixup flow cache part in xfrm policy
Date: Tue, 14 Jan 2014 19:59:07 +0100 [thread overview]
Message-ID: <20140114185907.GB1971@kria> (raw)
In-Reply-To: <1389663588-29678-4-git-send-email-fan.du@windriver.com>
2014-01-14, 09:39:46 +0800, Fan Du wrote:
> Bump flow cache genid, and flush flow cache should also be made
> in per net style.
>
> Signed-off-by: Fan Du <fan.du@windriver.com>
> ---
> net/xfrm/xfrm_policy.c | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/net/xfrm/xfrm_policy.c b/net/xfrm/xfrm_policy.c
> index e205c4b..d39c90f 100644
> --- a/net/xfrm/xfrm_policy.c
> +++ b/net/xfrm/xfrm_policy.c
> @@ -661,7 +661,7 @@ int xfrm_policy_insert(int dir, struct xfrm_policy *policy, int excl)
> hlist_add_head(&policy->bydst, chain);
> xfrm_pol_hold(policy);
> net->xfrm.policy_count[dir]++;
> - atomic_inc(&flow_cache_genid);
> + atomic_inc(&net->xfrm.flow_cache_genid);
>
> /* After previous checking, family can either be AF_INET or AF_INET6 */
> if (policy->family == AF_INET)
> @@ -2567,14 +2567,14 @@ static void __xfrm_garbage_collect(struct net *net)
>
> void xfrm_garbage_collect(struct net *net)
> {
> - flow_cache_flush();
> + flow_cache_flush(net);
> __xfrm_garbage_collect(net);
> }
> EXPORT_SYMBOL(xfrm_garbage_collect);
>
> static void xfrm_garbage_collect_deferred(struct net *net)
> {
> - flow_cache_flush_deferred();
> + flow_cache_flush_deferred(net);
> __xfrm_garbage_collect(net);
> }
>
> @@ -2947,6 +2947,7 @@ static int __net_init xfrm_net_init(struct net *net)
> spin_lock_init(&net->xfrm.xfrm_policy_sk_bundle_lock);
> mutex_init(&net->xfrm.xfrm_cfg_mutex);
>
> + flow_cache_init(net);
> return 0;
>
> out_sysctl:
You didn't address Cong Wang's comments for v1:
2014-01-13, 11:42:47 -0800, Cong Wang wrote:
> On Sun, Jan 12, 2014 at 11:49 PM, Fan Du <fan.du@windriver.com> wrote:
> > void xfrm_garbage_collect(struct net *net)
> > {
> > - flow_cache_flush();
> > + flow_cache_flush(net);
> > __xfrm_garbage_collect(net);
> > }
> > EXPORT_SYMBOL(xfrm_garbage_collect);
> >
> > static void xfrm_garbage_collect_deferred(struct net *net)
> > {
> > - flow_cache_flush_deferred();
> > + flow_cache_flush_deferred(net);
> > __xfrm_garbage_collect(net);
> > }
> >
>
> You changed the prototypes of flow_cache_flush*() in the previous
> patch, so, here you break bisect. They have to be in one commit.
--
Sabrina
next prev parent reply other threads:[~2014-01-14 18:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-14 1:39 [PATCHv2 net-next 0/4] Make flow cache name space aware Fan Du
2014-01-14 1:39 ` [PATCHv2 net-next 1/4] flowcache: Namespacify flowcache global parameters with xfrm Fan Du
2014-01-14 18:53 ` Sabrina Dubroca
2014-01-14 1:39 ` [PATCHv2 net-next 2/4] flowcache: Make flowcache entry inserting/flushing in per-net style Fan Du
2014-01-14 1:39 ` [PATCHv2 net-next 3/4] flowcache: Fixup flow cache part in xfrm policy Fan Du
2014-01-14 18:59 ` Sabrina Dubroca [this message]
2014-01-15 7:19 ` Fan Du
2014-01-14 1:39 ` [PATCHv2 net-next 4/4] flowcache: Bring net/core/flow.c under IPsec maintain scope Fan Du
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=20140114185907.GB1971@kria \
--to=sd@queasysnail.net \
--cc=davem@davemloft.net \
--cc=fan.du@windriver.com \
--cc=netdev@vger.kernel.org \
--cc=steffen.klassert@secunet.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