From: roopa <roopa@cumulusnetworks.com>
To: David Miller <davem@davemloft.net>
Cc: tgraf@suug.ch, hannes@stressinduktion.org, rshearma@brocade.com,
stephen@networkplumber.org, kuznet@ms2.inr.ac.ru,
jon.maloy@ericsson.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next v5 0/2] af_mpls: fix undefined reference to ip6_route_output with CONFIG_IPV6=n
Date: Thu, 30 Jul 2015 06:22:55 -0700 [thread overview]
Message-ID: <55BA252F.3070601@cumulusnetworks.com> (raw)
In-Reply-To: <20150729.224223.1592092790674598920.davem@davemloft.net>
On 7/29/15, 10:42 PM, David Miller wrote:
> From: Roopa Prabhu <roopa@cumulusnetworks.com>
> Date: Tue, 28 Jul 2015 15:27:39 -0700
>
>> v4 - v5: Use ipv6_stub_impl.ipv6_dst_lookup as suggested by Hannes
> I think this might not work.
>
> The ipv6_stub pointer is NULL until the ipv6 module is loaded.
>
> VXLAN can safely call through ipv6_stub->foo() because it _knows_ the
> ipv6 module has been loaded, and will not go away, because it is
> working with an ipv6 socket.
>
> You don't have that set of preconditions here, and thus it is pretty
> easy to generate a scenerio where ipv6_stub will be NULL at your call
> sites.
v4 seems to be a better/safe option in that case. I can resubmit v4 if
that is acceptable.
>
> This is starting to get really messy, to be honest. And we've been
> harboring this build failure for several days now.
>
please revert the commit that introduced the IPV6 dependency. I will
resubmit if needed.
I don't feel good about the build failure either.
Thanks and apologies.
commit 01faef2cebae02685e2bcfc9bbee8416d5ec19fc
Author: Roopa Prabhu <roopa@cumulusnetworks.com>
Date: Tue Jul 21 09:16:24 2015 -0700
mpls: make RTA_OIF optional
If user did not specify an oif, try and get it from the via address.
If failed to get device, return with -ENODEV.
next prev parent reply other threads:[~2015-07-30 13:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-28 22:27 [PATCH net-next v5 0/2] af_mpls: fix undefined reference to ip6_route_output with CONFIG_IPV6=n Roopa Prabhu
2015-07-30 5:42 ` David Miller
2015-07-30 13:22 ` roopa [this message]
2015-07-30 14:57 ` Hannes Frederic Sowa
2015-07-30 20:38 ` roopa
2015-07-30 21:02 ` David Miller
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=55BA252F.3070601@cumulusnetworks.com \
--to=roopa@cumulusnetworks.com \
--cc=davem@davemloft.net \
--cc=hannes@stressinduktion.org \
--cc=jon.maloy@ericsson.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@vger.kernel.org \
--cc=rshearma@brocade.com \
--cc=stephen@networkplumber.org \
--cc=tgraf@suug.ch \
/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).