linux-kernel - Re: [PATCHSET] fix CGROUP VS RCU

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Fri, 21 Nov 2008 17:14:24 +0800
From:	Lai Jiangshan <laijs@...fujitsu.com>
To:	Lai Jiangshan <laijs@...fujitsu.com>
CC:	Andrew Morton <akpm@...ux-foundation.org>,
	Paul Menage <menage@...gle.com>,
	Linux Containers <containers@...ts.linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
	Serge Hallyn <serue@...ibm.com>
Subject: Re: [PATCHSET] fix CGROUP VS RCU

Lai Jiangshan wrote:
> Andrew Morton wrote:
>> On Fri, 21 Nov 2008 16:49:13 +0800 Lai Jiangshan <laijs@...fujitsu.com> wrote:
>>
>>> current some cgroup struct are protected by RCU.
>>>
>>> struct protected by RCU:
>>> 	struct css_set, struct cgroup_subsys_state, struct cgroup
>>>
>>> pointer protected by RCU:
>>> 	struct task_struct.cgroups, struct css_set.subsys[*],
>>> 	struct cgroup_subsys_state.cgroup
>>> the last two pointers are readonly pointer!
>>>
>>> these patches are fix these structs, and pointers. And a faker:
>>> struct cgroup_subsys.root
>>>
>>> Not cleanup all yet.
>>>
>> These patches aren't sequence numbered.  In what order should they be
>> applied?
>>
>>
>>
>>
> 
> No order number, they are dependent(except 2 patches which have order number).

                            dependent --> independent

> 
> Lai.
> 
> 


--
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/