Re: [PATCH 1/2] [NETFILTER]: xt_socket: rename from xt_owner

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Jan 24 2008 08:54, Patrick McHardy wrote:
> Jan Engelhardt wrote:
>> commit 7ed2d25d54b696074c8e787a03a1513d245e8caa
>> Author: Jan Engelhardt <jengelh@xxxxxxxxxxxxxxx>
>> Date:   Mon Jan 21 13:34:48 2008 +0100
>> 
>>     [NETFILTER]: xt_socket: rename from xt_owner
>>     
>>     xt_owner matches against the ownership of a socket. Currently this
>>     only work in the output path when skb->sk is set. I recalled tproxy's
>>     xt_socket, which does an explicit socket for the input path and
>>     thought that this could be useful for xt_owner. Both modules would
>>     then do a lookup, so let's just combine the code into one module.
>>     
>>     This patch renames xt_owner to xt_socket; the tproxy bits and input
>>     path socket lookup will be added when tproxy gets merged.
>
> This seems unnecessary. We can consider the rename once tproxy
> gets merged, but things are progressing very slowly.

Just my 2 £.

xt_owner:
- add xt_owner v1
- remove xt_owner v0 in 2009
- add xt_socket v0 (duplicate code/rename)
- remove xt_owner v1 a year later
- add input path processing

xt_socket:
- add xt_socket v0 now
- remove xt_owner v0 in 2009
- add input path processing (no interface changes)
-
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Netfitler Users]     [LARTC]     [Bugtraq]     [Yosemite Forum]

  Powered by Linux