From: Al Viro <viro@ftp.linux.org.uk>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: Sridhar Samudrala <sri@us.ibm.com>,
davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: [PATCH RESEND 1/2] in-kernel sockets API
Date: Tue, 8 Aug 2006 01:56:19 +0100 [thread overview]
Message-ID: <20060808005619.GN29920@ftp.linux.org.uk> (raw)
In-Reply-To: <20060807162033.3685924e@localhost.localdomain>
On Mon, Aug 07, 2006 at 04:20:33PM -0700, Stephen Hemminger wrote:
> Please consider EXPORT_SYMBOL_GPL because this interface would be a obvious
> target for binary modules writers to use.
As opposed to duplicating it? WTFPoint of restriction that is trivial to
bypass? Look at those functions; there's nothing that couldn't be
immediately open-coded in a binary module and use of _GPL doesn't serve
any purpose.
next prev parent reply other threads:[~2006-08-08 0:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-07 23:00 [PATCH RESEND 1/2] in-kernel sockets API Sridhar Samudrala
2006-08-07 23:20 ` Stephen Hemminger
2006-08-08 0:46 ` Sridhar Samudrala
2006-08-08 0:56 ` Al Viro [this message]
2006-08-08 1:50 ` David Miller
2006-08-08 3:58 ` 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=20060808005619.GN29920@ftp.linux.org.uk \
--to=viro@ftp.linux.org.uk \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=shemminger@osdl.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).