From: Cong Wang <amwang@redhat.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
Ben Hutchings <bhutchings@solarflare.com>
Subject: Re: [PATCH net-next v10 03/11] ipv6: export a stub for IPv6 symbols used by vxlan
Date: Fri, 30 Aug 2013 15:47:47 +0800 [thread overview]
Message-ID: <1377848867.2591.5.camel@cr0> (raw)
In-Reply-To: <20130828091208.4bcaedcf@nehalam.linuxnetplumber.net>
On Wed, 2013-08-28 at 09:12 -0700, Stephen Hemminger wrote:
> On Wed, 28 Aug 2013 13:22:51 +0800
> Cong Wang <amwang@redhat.com> wrote:
>
> > +struct ipv6_stub {
> > + int (*ipv6_sock_mc_join)(struct sock *sk, int ifindex,
> > + const struct in6_addr *addr);
> > + int (*ipv6_sock_mc_drop)(struct sock *sk, int ifindex,
> > + const struct in6_addr *addr);
> > + int (*ipv6_dst_lookup)(struct sock *sk, struct dst_entry **dst,
> > + struct flowi6 *fl6);
> > + void (*udpv6_encap_enable)(void);
> > +};
> > +extern const struct ipv6_stub *ipv6_stub __read_mostly;
> > +
>
> Since IPv6 really can't ever be safely unloaded. why not:
> * admit that, and get rid of ipv6_module exit.
> * then this stub can be a static const table.
>
> You see virtual function tables that are writeable are potential malware
> targets, although eliminating all of them is impossible, I hate to
> see adding new ones.
I think getting rid of ipv6 exit deserves another thread for discussion,
not in this thread. Actually I raised same question before, but no one
replied me. If you want, I can send another patch for it after this
patchset gets merged.
Thanks!
next prev parent reply other threads:[~2013-08-30 7:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-28 5:22 [PATCH net-next v10 00/11] vxlan: add ipv6 support Cong Wang
2013-08-28 5:22 ` [PATCH net-next v10 01/11] ipv6: make ip6_dst_hoplimit() static inline Cong Wang
2013-08-28 10:39 ` Eric Dumazet
2013-08-28 5:22 ` [PATCH net-next v10 02/11] ipv6: move ip6_local_out into core kernel Cong Wang
2013-08-28 5:22 ` [PATCH net-next v10 03/11] ipv6: export a stub for IPv6 symbols used by vxlan Cong Wang
2013-08-28 16:12 ` Stephen Hemminger
2013-08-30 7:47 ` Cong Wang [this message]
2013-08-28 5:22 ` [PATCH net-next v10 04/11] ipv6: export some IPv6 special addresses to modules Cong Wang
2013-08-28 5:22 ` [PATCH net-next v10 05/11] ipv6: do not call ndisc_send_rs() with write lock Cong Wang
2013-08-28 15:34 ` Hannes Frederic Sowa
2013-08-28 5:22 ` [PATCH net-next v10 06/11] vxlan: add ipv6 support Cong Wang
2013-08-28 5:22 ` [PATCH net-next v10 07/11] vxlan: add ipv6 route short circuit support Cong Wang
2013-08-28 16:08 ` Stephen Hemminger
2013-08-28 5:22 ` [PATCH net-next v10 08/11] ipv6: move in6_dev_finish_destroy() into core kernel Cong Wang
2013-08-28 5:22 ` [PATCH net-next v10 09/11] vxlan: add ipv6 proxy support Cong Wang
2013-08-28 16:13 ` Stephen Hemminger
2013-08-28 5:22 ` [PATCH net-next v10 10/11] vxlan: respect scope_id for ll addr Cong Wang
2013-08-29 21:20 ` David Stevens
2013-08-30 8:10 ` Cong Wang
2013-08-28 5:22 ` [PATCH net-next v10 11/11] ipv6: Add generic UDP Tunnel segmentation Cong Wang
2013-08-28 17:55 ` Pravin Shelar
2013-08-30 8:16 ` Cong Wang
2013-08-30 21:14 ` Pravin Shelar
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=1377848867.2591.5.camel@cr0 \
--to=amwang@redhat.com \
--cc=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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).