Re: [RFC][PATCH] identify in_dev_get rcu read-side critical sections

On Wed, Sep 28, 2005 at 07:51:10AM -0700, Paul E. McKenney wrote:
> 
> The reference-count approach is only guaranteed to work if the kernel
> thread that did the reference-count increment is later referencing that
> same data element.  Otherwise, one has the following possible situation
> on DEC Alpha:

You're quite right.  Without the rcu_dereference users of in_dev_get()
may see pre-initialisation contents of in_dev.

So these barriers are definitely needed.

Thanks,
-- 
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <[email protected]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
-
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/

---

• References:
  • Re: [RFC][PATCH] identify in_dev_get rcu read-side critical sections
    • From: "David S. Miller" <[email protected]>
  • Re: [RFC][PATCH] identify in_dev_get rcu read-side critical sections
    • From: Herbert Xu <[email protected]>
  • Re: [RFC][PATCH] identify in_dev_get rcu read-side critical sections
    • From: "Paul E. McKenney" <[email protected]>

• Prev by Date: Re: I request inclusion of SAS Transport Layer and AIC-94xx into the kernel
• Next by Date: Re: [PATCH 3/3] Gdt hotplug
• Previous by thread: Re: [RFC][PATCH] identify in_dev_get rcu read-side critical sections
• Next by thread: Re: [RFC][PATCH] identify in_dev_get rcu read-side critical sections
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]