netdev - Re: why is it not allowed to add a new socket protocol family as an external module?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20130220.200502.1241369422255314068.davem@davemloft.net>
Date:	Wed, 20 Feb 2013 20:05:02 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	chris.friesen@...band.com
Cc:	stephen@...workplumber.org, netdev@...r.kernel.org
Subject: Re: why is it not allowed to add a new socket protocol family as
 an external module?

From: Chris Friesen <chris.friesen@...band.com>
Date: Wed, 20 Feb 2013 18:44:50 -0600

> On 02/20/2013 05:23 PM, Stephen Hemminger wrote:
>> On Wed, 20 Feb 2013 10:56:13 -0600
>> Chris Friesen<chris.friesen@...band.com>  wrote:
>>
>>> Hi,
>>>
>>> I was just wondering why the kernel doesn't allow a new network
>>> protocol
>>> family to be loaded as as a kernel module built outside the kernel
>>> source tree.
> 
>> If you want an answer, to the question, use a tool like cscope and
>> learn to read the kernel code. There are several tables of pointers
>> sized by NPROTO.
> 
> That's a bit insulting, don't you think?

Absolutely not insulting at all.

The list is _NOT_ a place to go when you're just too damn lazy to take
the 10 seconds it would have taken to answer your question with a
quick NPROTO grep on the kernel sources.

Stephen's response to you was therefore %100 appropriate, and I would
have told you likewise if I had been the first to respond.

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html