netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nicolas Dichtel <nicolas.dichtel@6wind.com>
To: Fan Du <fan.du@windriver.com>
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: [DISCUSSION] rt6i_genid
Date: Thu, 18 Jul 2013 11:13:20 +0200	[thread overview]
Message-ID: <51E7B1B0.3000109@6wind.com> (raw)
In-Reply-To: <51E75F82.4080300@windriver.com>

Le 18/07/2013 05:22, Fan Du a écrit :
> Hello Nicolas
>
> Commit 6f3118b571b8a4c06c7985dc3172c3526cb86253: "ipv6: use net->rt_genid to
> check dst validity"
> makes ip6_dst_check to check rt6i_genid against with struct net->rt_genid,
> As a matter of fact, struct net->rt_genid could only be modified by two places,
> first is adding/delete IPv4 address, second is inserting new XFRM policy.
>
> Is there any other considerations that adding/deleting IPv4 address would
> invalid all IPv6 dst
> as well? because I'm working a patch which actually depends on the result of
> this question.
No, the goal was to cover the IPsec case, ie invalidate dst entries when an xfrm 
policy is inserted/deleted.


Regards,
Nicolas

  reply	other threads:[~2013-07-18  9:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-18  3:22 [DISCUSSION] rt6i_genid Fan Du
2013-07-18  9:13 ` Nicolas Dichtel [this message]
2013-07-18  9:28   ` Fan Du
2013-07-18 15:12     ` Nicolas Dichtel
2013-07-19  0:01       ` Fan Du
2013-07-19  3:18         ` David Miller
2013-07-19  3:28           ` Fan Du
2013-07-19  3:31             ` David Miller
2013-07-19  7:50               ` Fan Du
2013-07-19  9:33                 ` David Miller
2013-07-22  5:43                   ` [RFC PATCH net-next] net: split rt_genid for ipv4 and ipv6 Fan Du
2013-07-22 10:53                     ` Steffen Klassert
2013-07-22 20:40                     ` Nicolas Dichtel

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=51E7B1B0.3000109@6wind.com \
    --to=nicolas.dichtel@6wind.com \
    --cc=fan.du@windriver.com \
    --cc=netdev@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).