linux-kernel - Re: [PATCH] init()/fini() clean up in the crypto

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

Date:	Thu, 27 Mar 2008 15:40:36 +0100
From:	Bodo Eggert <7eggert@....de>
To:	Kamalesh Babulal <kamalesh@...ux.vnet.ibm.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Benjamin Herrenschmidt <benh@...abs.org>,
	linux-kernel@...r.kernel.org,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH] init()/fini() clean up in the crypto

Kamalesh Babulal <kamalesh@...ux.vnet.ibm.com> wrote:

> This patch cleanups the crypto code, replaces the init() and fini()  with the
> <algorithm name>_init/_fini

This part ist OK.

> or init/fini_<algorithm name> (if the 
> <algorithm name>_init/_fini exist)

Having init_foo and foo_init won't be a good thing, will it? I'd start
confusing them.

What about foo_modinit instead?

¢¢

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