From: Florian Westphal <fw at strlen.de>
To: mptcp at lists.01.org
Subject: [MPTCP] Re: [RFC 1/2] mptcp: Export low-level routines for IPv6
Date: Thu, 17 Oct 2019 11:40:47 +0200 [thread overview]
Message-ID: <20191017094047.GW25052@breakpoint.cc> (raw)
In-Reply-To: 6d88a1f22660614c3b22f2cb892386af6244e76f.camel@redhat.com
[-- Attachment #1: Type: text/plain, Size: 915 bytes --]
Paolo Abeni <pabeni(a)redhat.com> wrote:
> > -static void inet6_sk_rx_dst_set(struct sock *sk, const struct sk_buff *skb)
> > +void inet6_sk_rx_dst_set(struct sock *sk, const struct sk_buff *skb)
> > {
> > struct dst_entry *dst = skb_dst(skb);
> >
> > @@ -111,6 +111,7 @@ static void inet6_sk_rx_dst_set(struct sock *sk, const struct sk_buff *skb)
> > tcp_inet6_sk(sk)->rx_dst_cookie = rt6_get_cookie(rt);
> > }
> > }
> > +EXPORT_SYMBOL(inet6_sk_rx_dst_set);
>
> I think this is not needed, as we don't build mptcp as a module.
> Dropping the 'static' scope should suffice. This should apply also to
> tcp_request_sock_ipv6_ops, tcp_v6_syn_recv_sock and ipv6_specific
> below.
Yes, but ipv6 can be built as a module, i.e. mptcp cannot call any ipv6
related symbol directly.
This will need rather ugly indirections, similar to
include/linux/netfilter_ipv6.h / "struct nf_ipv6_ops".
next reply other threads:[~2019-10-17 9:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-17 9:40 Florian Westphal [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-10-29 8:10 [MPTCP] Re: [RFC 1/2] mptcp: Export low-level routines for IPv6 Paolo Abeni
2019-10-28 23:46 Peter Krystad
2019-10-17 10:11 Paolo Abeni
2019-10-17 9:12 Paolo Abeni
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=20191017094047.GW25052@breakpoint.cc \
--to=unknown@example.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.