linux-kernel - cpu_active vs pcrypt & padata

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

Date:	Fri, 16 Mar 2012 11:13:08 +0100
From:	Peter Zijlstra <peterz@...radead.org>
To:	Steffen Klassert <steffen.klassert@...unet.com>
Cc:	Ingo Molnar <mingo@...e.hu>, Thomas Gleixner <tglx@...utronix.de>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: cpu_active vs pcrypt & padata

Hi Steffen,

I found cpu_active usage in crypto/pcrypt.c and was wondering what
that's doing there. I would really like to contain that thing to as
narrow a piece of kernel as I possible can (sched/cpuset/hotplug) but it
appears to be spreading.

Also, wth is all this kernel/padata.c stuff? There's next to no useful
comment in there and the only consumer seems to be pcrypt, does that
really need to be in kernel/ ?
--
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/