linux-kernel - [GIT PULL] cgroup fixes for v3.7-rc2

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>] [day] [month] [year] [list]

Message-ID: <20121024195441.GI12182@atj.dyndns.org>
Date:	Wed, 24 Oct 2012 12:54:41 -0700
From:	Tejun Heo <tj@...nel.org>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	linux-kernel@...r.kernel.org, Li Zefan <lizefan@...wei.com>,
	containers@...ts.linux-foundation.org, cgroups@...r.kernel.org
Subject: [GIT PULL] cgroup fixes for v3.7-rc2

Hello, Linus.

This pull request contains three fixes.  Two are reverts of
task_lock() removal in cgroup fork path.  The optimizations
incorrectly assumed that threadgroup_lock can protect process forks
(as opposed to thread creations) too.  Further cleanup of cgroup fork
path is scheduled.  The third fixes cgroup emptiness notification
loss.

Please pull from the following git branch to receive the above
changes.

  git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup.git for-3.7-fixes

for you to fetch changes up to d87838321124061f6c935069d97f37010fa417e6:

  Revert "cgroup: Remove task_lock() from cgroup_post_fork()" (2012-10-19 14:09:35 -0700)

----------------------------------------------------------------
Daisuke Nishimura (1):
      cgroup: notify_on_release may not be triggered in some cases

Tejun Heo (2):
      Revert "cgroup: Drop task_lock(parent) on cgroup_fork()"
      Revert "cgroup: Remove task_lock() from cgroup_post_fork()"

 kernel/cgroup.c | 41 ++++++++++-------------------------------
 1 file changed, 10 insertions(+), 31 deletions(-)

Thanks.

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