From: Simon Horman <horms@verge.net.au>
To: David Miller <davem@davemloft.net>
Cc: ja@ssi.bg, netdev@vger.kernel.org,
netfilter-devel@vger.kernel.org, lvs-devel@vger.kernel.org,
yoshfuji@linux-ipv6.org
Subject: Re: [PATCH net 0/3] ipv6: use rt6i_gateway as nexthop
Date: Mon, 28 Oct 2013 10:28:15 +0900 [thread overview]
Message-ID: <20131028012815.GL849@verge.net.au> (raw)
In-Reply-To: <20131021.184057.328665907625927061.davem@davemloft.net>
On Mon, Oct 21, 2013 at 06:40:57PM -0400, David Miller wrote:
> From: Julian Anastasov <ja@ssi.bg>
> Date: Sun, 20 Oct 2013 15:43:02 +0300
>
> > I see the following two alternatives for applying these
> > patches:
> >
> > 1. Linger patch 2 in net-next to avoid surprises in the upcoming
> > release. In this case patch 3 can be reworked not to depend on
> > the new rt6_nexthop() definition in patch 2. I guess this is a
> > better option, so that patch 2 can be reviewed and tested for
> > longer time.
> >
> > 2. Include all 3 patches in net tree - more risky because this
> > is my first attempt to change IPv6.
>
> I have decided to merge all three patches into -net right now.
> I've reviewed these patches several times and they look good
> to me.
>
> I'll let them cook upstream for at least a week before submitting them
> to -stable to let any last minute errors show themselves and
> subsequently get resolved.
Thanks Dave,
FWIW, I have verified that these changes resolve the problem
that I reported with IPVS that I believe prompted Julian to write
these changes. That is IPv6 IPVS-DR once again works with these
changes in place.
prev parent reply other threads:[~2013-10-28 1:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-20 12:43 [PATCH net 0/3] ipv6: use rt6i_gateway as nexthop Julian Anastasov
2013-10-20 12:43 ` [PATCH net 1/3] ipv6: always prefer rt6i_gateway if present Julian Anastasov
2013-10-21 5:00 ` Hannes Frederic Sowa
2013-10-20 12:43 ` [PATCH net 2/3] ipv6: fill rt6i_gateway with nexthop address Julian Anastasov
2013-10-20 18:33 ` Hannes Frederic Sowa
2013-10-21 5:01 ` Hannes Frederic Sowa
2013-10-21 7:31 ` Julian Anastasov
2013-10-21 22:42 ` David Miller
2013-10-20 12:43 ` [PATCH net 3/3] netfilter: nf_conntrack: fix rt6i_gateway checks for H.323 helper Julian Anastasov
2013-10-21 5:04 ` Hannes Frederic Sowa
2013-10-21 9:35 ` [PATCH net 0/3] ipv6: use rt6i_gateway as nexthop Hannes Frederic Sowa
2013-10-21 20:02 ` Julian Anastasov
2013-10-21 22:40 ` David Miller
2013-10-28 1:28 ` Simon Horman [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=20131028012815.GL849@verge.net.au \
--to=horms@verge.net.au \
--cc=davem@davemloft.net \
--cc=ja@ssi.bg \
--cc=lvs-devel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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).