linux-kernel - Re: [PATCH 31/73] module: relocate module

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]

Message-ID: <CAP=VYLrqs_EkpCZ5mhD3C+FygR7Ekg1Cp_2T4npxa0c9dj-C-g@mail.gmail.com>
Date:	Tue, 21 Jan 2014 20:56:24 -0500
From:	Paul Gortmaker <paul.gortmaker@...driver.com>
To:	Rusty Russell <rusty@...tcorp.com.au>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	linux-arch <linux-arch@...r.kernel.org>
Subject: Re: [PATCH 31/73] module: relocate module_init from init.h to module.h

On Tue, Jan 21, 2014 at 7:16 PM, Rusty Russell <rusty@...tcorp.com.au> wrote:
> Paul Gortmaker <paul.gortmaker@...driver.com> writes:
>> Modular users will always be users of init functionality, but
>> users of init functionality are not necessarily always modules.
>>
>> Hence any functionality like module_init and module_exit would
>> be more at home in the module.h file.  And module.h should
>> explicitly include init.h to make the dependency clear.
>>
>> We've already done all the legwork needed to ensure that this
>> move does not cause any build regressions due to implicit
>> header file include assumptions about where module_init lives.
>>
>> Cc: Rusty Russell <rusty@...tcorp.com.au>
>> Signed-off-by: Paul Gortmaker <paul.gortmaker@...driver.com>
>
> Acked-by: Rusty Russell <rusty@...tcorp.com.au>
>
> Want to delete the extraneous semicolons, for bonus points? :)
>
>> +#define module_init(x)       __initcall(x);

I would if I could, but as I was discussing on irc with hpa about a
week ago, there are ~600 users of module_init who are relying on
that extra ";" that we need to fix 1st...  :-)    [on my todo list!]

Thanks for the review; much appreciated,
Paul.
--

> ...
>> +#define module_exit(x)       __exitcall(x);
>
> Cheers,
> Rusty.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-arch" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
--
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/