From: Armin Abfalterer <armina@ifi.uio.no>
To: netdev@vger.kernel.org
Subject: tcp_sock variable initialization
Date: Fri, 18 Sep 2009 10:50:59 +0200 [thread overview]
Message-ID: <1253263859.4539.31.camel@localhost.localdomain> (raw)
Hi!
I need a control variable (ecnn_flags) in tcp_sock that should be set
properly after the 3-way-handshake in tcp_create_openreq_child(). If I
set the variable in its value is always 0 afterwards.
struct sock *tcp_create_openreq_child( ... )
{
struct sock *newsk = inet_csk_clone(sk, req, GFP_ATOMIC);
if (newsk != NULL) {
struct tcp_sock *newtp;
newtp = tcp_sk(newsk);
newtp->ecnn_flags |= TCP_ECN_NONCE_OK;
}
}
When I read the variable for the next outgoing segment the values is not
set.
static int tcp_transmit_skb( ... )
{
struct tcp_sock *tp;
if (tp->ecnn_flags & TCP_ECN_NONCE_OK) {
/*
* never entered!!!!
*/
}
}
I'm quite sure that it has to do with the creation of the big socket
when the connection enters TCP_ESTABLISHED but searching for hours
didn't help to find the right place where my variable is re-initialized.
Any hint in the right direction would greatly appreciated!!! Thanks!
Armin
reply other threads:[~2009-09-18 8:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1253263859.4539.31.camel@localhost.localdomain \
--to=armina@ifi.uio.no \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).