From: "David S. Miller" <davem@redhat.com>
To: Michael Rozhavsky <mike@minantech.com>
Cc: netdev@oss.sgi.com
Subject: Re: [PATCH] fix locking
Date: Thu, 11 Sep 2003 16:49:03 -0700 [thread overview]
Message-ID: <20030911164903.63f0010b.davem@redhat.com> (raw)
In-Reply-To: <20030906002649.GA32369@server-mrozhavsky.dyndns.org>
On Fri, 5 Sep 2003 17:26:49 -0700
Michael Rozhavsky <mike@minantech.com> wrote:
> I've found two problems with locking in networking code.
Not applied, in both cases a higher order lock guarentees
that nobody else can add elements to the list.
We only need to lock to make sure readers (who don't take
the higher level lock) see a consistent list state.
In the tcp_ipv4.c case, the higher level lock is the listening
socket lock. In the sit.c case the higher level lock is the
RTNL semaphore.
prev parent reply other threads:[~2003-09-11 23:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-06 0:26 [PATCH] fix locking Michael Rozhavsky
2003-09-09 2:21 ` David S. Miller
2003-09-11 23:49 ` 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=20030911164903.63f0010b.davem@redhat.com \
--to=davem@redhat.com \
--cc=mike@minantech.com \
--cc=netdev@oss.sgi.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 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).