Re: On "Unreliable Locking Guide" bug ?

• Next message: Paul Gortmaker: "Re: /dev/rtc not working on ASUS A7V133"
• Previous message: Matti Aarnio: "Re: lkml subject line"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

In message <3A89CAA7.5090400@oz.agile.tv> you write:
> Hi Paul,
>
> I am reviewing your "Unreliable Locking Guide" from linux 2.4 and just
> wonder about the
> section on "Avoiding Locks: Read and Write". The two lines of code
>
> new->next = i-> next;
> i->next = new;

Hi John,

        Yes, there is of course a lock against other list
manipulations. I've attached a patch to make this clear..

Thanks!
Rusty.

--- linux-2.4.0-official/Documentation/DocBook/kernel-locking.tmpl.~1~ Sat Dec 30 09:07:19 2000
+++ linux-2.4.0-official/Documentation/DocBook/kernel-locking.tmpl Wed Feb 14 15:33:36 2001
@@ -720,7 +720,8 @@
       halves without a lock. Depending on their exact timing, they
       would either see the new element in the list with a valid
       <structfield>next</structfield> pointer, or it would not be in the
- list yet.
+ list yet. A lock is still required against other CPUs inserting
+ or deleting from the list, of course.
     </para>
 
     <para>

--
Premature optmztion is rt of all evl. --DK
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

• Next message: Paul Gortmaker: "Re: /dev/rtc not working on ASUS A7V133"
• Previous message: Matti Aarnio: "Re: lkml subject line"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Thu Feb 15 2001 - 21:00:23 EST