Re: Segfault hidden in list.h

David S. Miller (davem@redhat.com)
Sun, 12 May 2002 17:50:21 -0700 (PDT)


From: Linus Torvalds <torvalds@transmeta.com>
Date: Sun, 12 May 2002 17:59:27 -0700 (PDT)

If the coder doesn't lock his data structures, it doesn't matter _what_
order we execute the list modifications in - different architectures will
do different thing with inter-CPU memory ordering, and trying to order
memory accesses on a source level is futile.

However, if the list manipulation had some memory barriers
added to it...

The people doing the lockless reader RCU stuff could benefit from such
an interface.
-
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/