From: "David S. Miller" <davem@redhat.com>
To: Paul Wagland <paul@wagland.net>
Cc: vcanja@bitdefender.com, linux-kernel@vger.kernel.org
Subject: Re: problem in tcp_v4_synq_add ?
Date: Wed, 10 Mar 2004 13:37:34 -0800 [thread overview]
Message-ID: <20040310133734.0758f5e2.davem@redhat.com> (raw)
In-Reply-To: <F750F6B1-7271-11D8-AFFE-000A95CD704C@wagland.net>
On Wed, 10 Mar 2004 10:04:41 +0100
Paul Wagland <paul@wagland.net> wrote:
> > Nope, the listening socket's socket lock is held, and all things that
> > add members to these hash chains hold that lock.
>
> Is that the same as saying that the write_lock() is not needed at all?
> Since it is already guaranteed to be protected with a different lock?
Also not true, as other pieces of code traverse the list as a reader
without holding the listening sockets lock.
prev parent reply other threads:[~2004-03-10 21:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-09 11:27 problem in tcp_v4_synq_add ? Viorel Canja, Softwin
2004-03-09 19:30 ` David S. Miller
2004-03-10 9:04 ` Paul Wagland
2004-03-10 11:42 ` Re[2]: " Viorel Canja, Softwin
2004-03-10 21:37 ` David S. Miller [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=20040310133734.0758f5e2.davem@redhat.com \
--to=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paul@wagland.net \
--cc=vcanja@bitdefender.com \
/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.