Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751048AbWCYSjc (ORCPT ); Sat, 25 Mar 2006 13:39:32 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751058AbWCYSjc (ORCPT ); Sat, 25 Mar 2006 13:39:32 -0500 Received: from linux01.gwdg.de ([134.76.13.21]:23183 "EHLO linux01.gwdg.de") by vger.kernel.org with ESMTP id S1751048AbWCYSjb (ORCPT ); Sat, 25 Mar 2006 13:39:31 -0500 Date: Sat, 25 Mar 2006 19:39:06 +0100 (MET) From: Jan Engelhardt To: Benjamin cc: linux-kernel@vger.kernel.org Subject: Re: Modify the sock Structure!! In-Reply-To: <4424ED2A.3040006@tamu.edu> Message-ID: References: <4424ED2A.3040006@tamu.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 764 Lines: 24 > Hello! I try to modify the sock Structure in sock.h in order to record some > data! > I just add a unsigned short in the end of the structure. such as: > > struct sock { > safe or not. Is there any side-effect? Or I need to add additional code to > avoid some unexpected > situation? Thank you very much! Should be ok. For example, ipt_TPROXY/ipt_tproxy also adds something to struct sock (including enlarging fields in the middle of the struct); I have not experienced any problem with it. Jan Engelhardt -- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/