tcp_hashinfo exported or not?

tcp_hashinfo exported or not?

[Shaya Potter]

I'm having some slight issues with using tcp_hashinfo in 2.4.19.  It
appears to be exported (net/netsyms.c), appears in the System.map
generated, but when I try to load a module that makes use of it, insmod
claims it isn't there (and isn't listed in /proc/ksyms either,
explaining why insmod complains).

Is there any voodoo that I have to do to make use of this symbol in a
module?

thanks,

shaya

Re: tcp_hashinfo exported or not?

[David S. Miller]

It's only exported when IPV6 is enabled as a module.

Re: tcp_hashinfo exported or not?

[Chris Wedgwood]

On Tue, Aug 27, 2002 at 08:42:59PM -0700, David S. Miller wrote:

    It's only exported when IPV6 is enabled as a module.

Conditionally exporting symbols based upon CONFIG_* is a PITA.  Do we
really need to do this and will you accept a patch making go away?

It's nice to be able to build a module outside of the kernel source
and not have to rebuild the kernel to get access to symbols.



  --cw

Re: tcp_hashinfo exported or not?

[David S. Miller]

   From: Chris Wedgwood <cw@f00f.org>
   Date: Wed, 28 Aug 2002 15:09:35 -0700

   Conditionally exporting symbols based upon CONFIG_* is a PITA.  Do we
   really need to do this and will you accept a patch making go away?
   
Nobody else should need to get at the TCP hash tables.

Are you trying to work on a proprietary binary-only implementation of
Linux IPv6 TCP :-)

Franks a lot,
David S. Miller
davem@redhat.com