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: <b741c2440911012344n7a6f7241ma873abac2fc9507e@mail.gmail.com>
Date:	Mon, 2 Nov 2009 15:44:22 +0800
From:	Liu Aleaxander <aleaxander@...il.com>
To:	menage@...gle.com, lizf@...fujitsu.com,
	linux-kernel@...r.kernel.org
Subject: [PATCH 0/3] Fix the 'current css_set' problem in debug subsystem

Hello all.

(Sorry for the resending, it seems I opened the HTML encoding before)

This a three-patch set to fix the 'current css_set' problem in debug
subsystem of cgroup system. (well, in fact, it's a two-patch set; the
third one just fixes a typo).

Say I mount a cgroup fs in /cgroup, and here is the problem:
$ cat debug.current_css_set_refcount
268
$ mkdir test
$ cd test
$ cat debug.curernt_css_set_refcount
268

$ echo $$ > tasks
$ cat debug.current_css_set_refcount
2
$ cd ../
$ cat debug.current_css_set_refcount
2

That means it always print the css_set_refcount of the cgroup that
comprise the current task(bash, here), instead of the current cgroup
whatever cgroup you are in. And this would be meaningless to put the
same content in all the cgroups. So, to make it more meaningful, we
should make it print the css_set_refcount of the cgroup you are
currently in.

Patch 1 adds a cgroup_first_css_set function to get the current
css_set of one cgroup.
Patch 2 fixes the problem.
Patch 3 just fixes a typo.

--
regards
Liu Aleaxander
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ