From: Aviv Greenberg <deca@netvision.net.il>
To: linux-kernel@vger.kernel.org
Subject: tcp_write_space
Date: Mon, 23 Jul 2001 12:37:02 +0300 [thread overview]
Message-ID: <01072312370200.19071@aviv_linuxddd> (raw)
Hi,
Why isn't the sk->callback_lock aquired in the tcp_write_space
callback ??
Is this intentional ?
--
- Aviv Greeberg
next reply other threads:[~2001-07-23 9:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-23 9:37 Aviv Greenberg [this message]
2001-07-23 22:53 ` tcp_write_space Alexey Kuznetsov
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=01072312370200.19071@aviv_linuxddd \
--to=deca@netvision.net.il \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.