In article <[EMAIL PROTECTED]> you wrote: > +Consider a typical block of kernel code: > + > + spin_lock(&the_lock); > + do_something_on(&shared_data); > + do_something_else_with(&shared_data); > + spin_unlock(&the_lock); > + > +If all the code follows the locking rules, the value of shared_data cannot > +change unexpectedly while the_lock is held.
Well maybe it is trivial, but I would add e.g. "all places where the shared_data is accessed must be protected by this spinlock" > + - The jiffies variable is special in that it can have a different value what about other atomic readable counters (like interface counters)? Gruss Bernd - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
