From mboxrd@z Thu Jan 1 00:00:00 1970 From: Patrick McHardy Subject: Re: [PATCH 1/2] [NETFILTER]: xt_socket: rename from xt_owner Date: Thu, 24 Jan 2008 08:54:56 +0100 Message-ID: <47984450.7070309@trash.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Cc: Netfilter Developer Mailing List To: Jan Engelhardt Return-path: Received: from stinky.trash.net ([213.144.137.162]:35061 "EHLO stinky.trash.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753389AbYAXHzq (ORCPT ); Thu, 24 Jan 2008 02:55:46 -0500 In-Reply-To: Sender: netfilter-devel-owner@vger.kernel.org List-ID: Jan Engelhardt wrote: > commit 7ed2d25d54b696074c8e787a03a1513d245e8caa > Author: Jan Engelhardt > 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.