[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4DAF7EAC.8010504@schaufler-ca.com>
Date: Wed, 20 Apr 2011 17:47:40 -0700
From: Casey Schaufler <casey@...aufler-ca.com>
To: Andi Kleen <andi@...stfloor.org>
CC: Andi Kleen <ak@...ux.intel.com>, jmorris@...ei.org,
linux-security-module@...r.kernel.org,
linux-kernel@...r.kernel.org,
Casey Schaufler <casey@...aufler-ca.com>
Subject: Re: [PATCH] SMACK: Add missing rcu_read_lock/unlock for process capability
walk.
On 4/20/2011 5:08 PM, Andi Kleen wrote:
>> The global list, yes. The task specific list, no. Modifying the local
>> list is like any other modification of the cred structure and requires
>> the cred be copied.
> But you still need to free it eventually right? And that freeing will
> need RCU on the reader.
Entries are never freed from the global list. Someone is working
on a patch to do that, but is running into - wait for it - locking
issues.
Entries on the local lists are only freed when the task exits.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists