linux-kernel - Re: [patch 128/197] freezer: add try_to

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 for Android: free password hash cracker in your pocket

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

Date:	Wed, 09 May 2007 20:48:02 +0200
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
CC:	ego@...ibm.com, Pavel Machek <pavel@....cz>,
	akpm@...ux-foundation.org, torvalds@...ux-foundation.org,
	James.Bottomley@...eleye.com, aneesh.kumar@...il.com,
	drzeus@...eus.cx, dwmw2@...radead.org, greg@...ah.com,
	mingo@...e.hu, neilb@...e.de, oleg@...sign.ru,
	paulmck@...ux.vnet.ibm.com, vatsa@...ibm.com,
	linux-kernel@...r.kernel.org
Subject: Re: [patch 128/197] freezer: add try_to_freeze calls to all kernel
 threads

Rafael J. Wysocki wrote:
> On Wednesday, 9 May 2007 17:29, Gautham R Shenoy wrote:
>> On Wed, May 09, 2007 at 03:20:47PM +0200, Stefan Richter wrote:
>>> Let me point out that the usual process would be
[...to do it in one go....]
>> Well, a couple of RFC's have already been sent with this regard.
>> Most of these recent freezer changes resulted due to the discussions
>> that took place over  these RFC's.
[...]
> I feel I ought to explain why it's ended up in this state.
> 
> This is not a new patch.  It's been in -mm since 2.6.21-rc2-mm1 (at least)
> and we hoped to have the selective freezing of the system for different events
> done before the 2.6.22 merging window would open.  It didn't happen, mainly
> for reasons that we couldn't control, and now we have some patches that
> depend on this one and are more urgent, since they're needed to fix some bugs.

OK, thanks once more for the explanations.

[...]
>> Will keep you posted on the freezer developments from now on.
> 
> Me too.

Well, the mistake on my part was that I didn't pull -mm regularly,
otherwise I would have automatically seen the change to the one kthread
I am interested in.

Thanks,
-- 
Stefan Richter
-=====-=-=== -=-= -=--=
http://arcgraph.de/sr/
-
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/