From: Benjamin <benchu@tamu.edu>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Modify the sock Structure!!
Date: Sat, 25 Mar 2006 13:05:45 -0600 [thread overview]
Message-ID: <44259489.4070507@tamu.edu> (raw)
In-Reply-To: <Pine.LNX.4.61.0603251938110.29793@yvahk01.tjqt.qr>
Cool! Thanks for the answer!
Best Regards,
Benjamin Chu
Jan Engelhardt wrote:
>> 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
>
prev parent reply other threads:[~2006-03-25 19:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-25 7:11 Modify the sock Structure!! Benjamin
2006-03-25 18:39 ` Jan Engelhardt
2006-03-25 19:05 ` Benjamin [this message]
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=44259489.4070507@tamu.edu \
--to=benchu@tamu.edu \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
/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