mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Gong Su <gongsu@cs.columbia.edu>
To: linux-kernel@vger.kernel.org
Subject: Replacing tcp_v4_rcv from a module
Date: Tue, 25 Nov 2003 03:21:05 -0500	[thread overview]
Message-ID: <200311250821.hAP8L6OW006754@sutton.cs.columbia.edu> (raw)

I need some customized function inside tcp_v4_rcv so I wrote a module to
replace tcp_protocol->handler with my own function pointer; and currently
my own tcp_v4_rcv is just a copy of the original tcp_v4_rcv. But as soon
as traffic came in, my machine locks up hard. I can't think of a reason
why it would do so since I've changed other functions the same way, e.g.,
replacing ip_packet_type->func with my own ip_rcv function pointer without
problem. Am I missing something obvious? Thanks for any enlightenment.

-- 
/Gong



             reply	other threads:[~2003-11-25  8:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-25  8:21 Gong Su [this message]
2003-11-25  9:29 ` Raj
2003-11-25 15:40   ` Gong Su

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=200311250821.hAP8L6OW006754@sutton.cs.columbia.edu \
    --to=gongsu@cs.columbia.edu \
    --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

all inboxes | Powered by JetHome®