From: Stephen Hemminger <shemminger@osdl.org>
To: Sridhar Samudrala <sri@us.ibm.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC/PATCH 1/2] in-kernel sockets API
Date: Tue, 13 Jun 2006 14:07:16 +0900 [thread overview]
Message-ID: <20060613140716.6af45bec@localhost.localdomain> (raw)
In-Reply-To: <1150156562.19929.32.camel@w-sridhar2.beaverton.ibm.com>
On Mon, 12 Jun 2006 16:56:01 -0700
Sridhar Samudrala <sri@us.ibm.com> wrote:
> This patch makes it convenient to use the sockets API by the in-kernel
> users like sunrpc, cifs & ocfs2 etc and any future users.
> Currently they get to this API by directly accesing the function pointers
> in the sock structure.
>
> Most of these functions are pretty simple and can be made inline and moved
> to linux/net.h.
...
> @@ -2176,3 +2279,13 @@ EXPORT_SYMBOL(sock_wake_async);
> EXPORT_SYMBOL(sockfd_lookup);
> EXPORT_SYMBOL(kernel_sendmsg);
> EXPORT_SYMBOL(kernel_recvmsg);
> +EXPORT_SYMBOL(kernel_bind);
> +EXPORT_SYMBOL(kernel_listen);
> +EXPORT_SYMBOL(kernel_accept);
> +EXPORT_SYMBOL(kernel_connect);
> +EXPORT_SYMBOL(kernel_getsockname);
> +EXPORT_SYMBOL(kernel_getpeername);
> +EXPORT_SYMBOL(kernel_getsockopt);
> +EXPORT_SYMBOL(kernel_setsockopt);
> +EXPORT_SYMBOL(kernel_sendpage);
> +EXPORT_SYMBOL(kernel_ioctl);
Don't we want to restrict this to GPL code with EXPORT_SYMBOL_GPL?
next prev parent reply other threads:[~2006-06-13 5:08 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-12 23:56 [RFC/PATCH 1/2] in-kernel sockets API Sridhar Samudrala
2006-06-13 5:07 ` Stephen Hemminger [this message]
2006-06-13 11:13 ` Arnaldo Carvalho de Melo
2006-06-13 11:22 ` Brian F. G. Bidulock
2006-06-13 21:12 ` Daniel Phillips
2006-06-13 21:40 ` Brian F. G. Bidulock
2006-06-13 22:00 ` Chase Venters
2006-06-13 22:30 ` Daniel Phillips
2006-06-13 22:47 ` Brian F. G. Bidulock
2006-06-13 23:59 ` Chase Venters
2006-06-14 0:31 ` Brian F. G. Bidulock
2006-06-14 0:53 ` Chase Venters
2006-06-14 6:07 ` Brian F. G. Bidulock
2006-06-14 7:58 ` Chase Venters
2006-06-14 9:28 ` Brian F. G. Bidulock
2006-06-14 10:43 ` Alan Cox
2006-06-14 10:54 ` Brian F. G. Bidulock
2006-06-14 10:36 ` Theodore Tso
2006-06-13 22:44 ` Brian F. G. Bidulock
2006-06-13 23:42 ` Ben Greear
2006-06-14 0:05 ` Chase Venters
2006-06-14 0:18 ` Brian F. G. Bidulock
2006-06-14 0:29 ` Chase Venters
2006-06-14 0:36 ` Brian F. G. Bidulock
2006-06-14 0:19 ` Ben Greear
2006-06-14 0:38 ` Brian F. G. Bidulock
2006-06-14 13:30 ` Harald Welte
2006-06-14 14:29 ` Erik Mouw
2006-06-14 15:26 ` Harald Welte
2006-06-14 17:48 ` Daniel Phillips
2006-06-14 18:03 ` Brian F. G. Bidulock
2006-06-14 20:52 ` Sridhar Samudrala
2006-06-13 14:58 ` Jan Engelhardt
2006-06-13 16:27 ` Sridhar Samudrala
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=20060613140716.6af45bec@localhost.localdomain \
--to=shemminger@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sri@us.ibm.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 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).