| To: | Michael Rozhavsky <mike@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [PATCH] fix locking |
| From: | "David S. Miller" <davem@xxxxxxxxxx> |
| Date: | Thu, 11 Sep 2003 16:49:03 -0700 |
| Cc: | netdev@xxxxxxxxxxx |
| In-reply-to: | <20030906002649.GA32369@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> |
| References: | <20030906002649.GA32369@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
On Fri, 5 Sep 2003 17:26:49 -0700 Michael Rozhavsky <mike@xxxxxxxxxxxxx> 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 in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH] convert packet scheduler API to single_open, David S. Miller |
|---|---|
| Next by Date: | Re: Trivial fix for wrong error message from icmp.c (2.6.0-test4), David S. Miller |
| Previous by Thread: | Re: [PATCH] fix locking, David S. Miller |
| Next by Thread: | [PATCH] 2.6.0-test4 SEQ_START_TOKEN Add #define to seq_file.h (1/6), Joe Perches |
| Indexes: | [Date] [Thread] [Top] [All Lists] |