linux-kernel - Re: [rfc v2 0/7] procfs fdinfo extension v2

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

Date:	Thu, 24 May 2012 11:01:21 -0700
From:	Matt Helsley <matthltc@...ibm.com>
To:	Cyrill Gorcunov <gorcunov@...nvz.org>
Cc:	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Pavel Emelyanov <xemul@...allels.com>,
	James Bottomley <jbottomley@...allels.com>,
	ebiederm@...ssion.com, tj@...nel.org, skinsbursky@...nvz.org
Subject: Re: [rfc v2 0/7] procfs fdinfo extension v2

On Wed, May 23, 2012 at 02:25:41PM +0400, Cyrill Gorcunov wrote:

<snip>

>  - finally it would be great to have ability to attach tasks to
>    frozen tasks cgroup to thaw them at one moment (the preliminary
>    patch I've proposed pretty long ago, but Tejun was modifying cgroups
>    code and asked to wait until 3.4 is release, so I didn't check
>    the current status of task cgroups at moment, I've it in my todo list)

This still strikes me as the wrong way to go about freezing for c/r.
You never explained why you had to do it this way. Why can't you inject
the parasite thread, move that thread out of the cgroup-to-be-frozen,
then freeze?

As best I can tell your reply last time only fleshed out the details
of *how* you would like it to work, not *why it needs to* work that way:

	http://lkml.org/lkml/2011/11/30/27

Cheers,
	-Matt Helsley

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