linux-kernel - Re: [PATCH v2] ramfs: Remove module leftovers

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:	Mon, 10 Oct 2011 13:13:22 +0200
From:	Richard Weinberger <richard@....at>
To:	Christoph Hellwig <hch@....de>
CC:	linux-kernel@...r.kernel.org, xiyou.wangcong@...il.com,
	viro@...iv.linux.org.uk, dchinner@...hat.com
Subject: Re: [PATCH v2] ramfs: Remove module leftovers

Am 10.10.2011 13:09, schrieb Christoph Hellwig:
> On Mon, Oct 10, 2011 at 12:54:39PM +0200, Richard Weinberger wrote:
>> Since ramfs is hard-selected to "y", the module leftovers make
>> no sense.
> 
> Removing the dead code looks good, but what is the point in using
> device_initcall?  We've always been using module_init for non-modular
> code, though.
> 

Ah, ok!
So we can keep the module_init()?
I was not sure whether it's valid to use module_init() in pure
non-modular code...

Thanks,
//richard


Download attachment "signature.asc" of type "application/pgp-signature" (491 bytes)