Re: [TOMOYO 05/15](repost) Domain transition handler functions.

In article <[email protected]> (at Wed, 3 Oct 2007 22:04:11 +0900), Tetsuo Handa <[email protected]> says:

> Well, is there a way to avoid read_lock when reading list?
> 
> Currently, TOMOYO Linux avoids read_lock, on the assumption that
> (1) First, ptr->next is initialized with NULL.
> (2) Later, ptr->next is assigned non-NULL address.
> (3) Assigning to ptr->next is done atomically.

RCU?

--yoshfuji
-
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: [TOMOYO 05/15](repost) Domain transition handler functions.
    • From: YOSHIFUJI Hideaki / 吉藤英明 <[email protected]>
  • Re: [TOMOYO 05/15](repost) Domain transition handler functions.
    • From: James Morris <[email protected]>
  • Re: [TOMOYO 05/15](repost) Domain transition handler functions.
    • From: Tetsuo Handa <[email protected]>

• Prev by Date: Re: top displaying 9999% CPU usage
• Next by Date: Re: [PATCH 1/3] signal(i386): alternative signal stack wraparound occurs
• Previous by thread: Re: [TOMOYO 05/15](repost) Domain transition handler functions.
• Next by thread: Re: [TOMOYO 05/15](repost) Domain transition handler functions.
• Index(es):
  • Date
  • Thread

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