netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Weiping Pan <panweiping3@gmail.com>
To: unlisted-recipients:; (no To-header on input)
Cc: Weiping Pan <panweiping3@gmail.com>,
	"David S. Miller" <davem@davemloft.net> (maintainer:NETWORKING
	[IPv4/...),
	Alexey Kuznetsov <kuznet@ms2.inr.ac.ru> (maintainer:NETWORKING
	[IPv4/...),
	James Morris <jmorris@namei.org> (maintainer:NETWORKING
	[IPv4/...),
	Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>
	(maintainer:NETWORKING [IPv4/...),
	Patrick McHardy <kaber@trash.net> (maintainer:NETWORKING
	[IPv4/...),
	netdev@vger.kernel.org (open list:NETWORKING [IPv4/...),
	linux-kernel@vger.kernel.org (open list)
Subject: [PATCH net] ipv6:export nd_tbl
Date: Tue,  6 Dec 2011 14:52:41 +0800	[thread overview]
Message-ID: <a46bd31bb9a4876e97f96e82d399a26506646d04.1323154266.git.panweiping3@gmail.com> (raw)

A customer wants to use nd_tbl in his kernel module,
the easiest way is to export nd_tbl, just as arp_tbl.

There were some requests to export nd_tbl, like:
http://marc.info/?l=netfilter-devel&m=111416950824614&w=2
http://marc.info/?l=linux-netdev&m=110715893206991&w=2

But they were all rejected.
I want to know the reason why can't nd_tbl be exported just as arp_tbl,
and how can we look up nd_tbl without exporting it.

thanks
Weiping Pan

Signed-off-by: Weiping Pan <panweiping3@gmail.com>
---
 net/ipv6/ndisc.c |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/net/ipv6/ndisc.c b/net/ipv6/ndisc.c
index 0cb78d7..1ab98b5 100644
--- a/net/ipv6/ndisc.c
+++ b/net/ipv6/ndisc.c
@@ -153,6 +153,7 @@ struct neigh_table nd_tbl = {
 	.gc_thresh2 =	 512,
 	.gc_thresh3 =	1024,
 };
+EXPORT_SYMBOL(nd_tbl);
 
 /* ND options */
 struct ndisc_options {
-- 
1.7.4.4

             reply	other threads:[~2011-12-06  6:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-06  6:52 Weiping Pan [this message]
2011-12-06 17:57 ` [PATCH net] ipv6:export nd_tbl 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=a46bd31bb9a4876e97f96e82d399a26506646d04.1323154266.git.panweiping3@gmail.com \
    --to=panweiping3@gmail.com \
    --cc=davem@davemloft.net \
    --cc=jmorris@namei.org \
    --cc=kaber@trash.net \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@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).