linux-kernel - Re: [RFC] __ref annotation of function/data referencing __init/_

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: <Pine.LNX.4.64.0801292053531.14907@fbirervta.pbzchgretzou.qr>
Date:	Tue, 29 Jan 2008 20:55:32 +0100 (CET)
From:	Jan Engelhardt <jengelh@...putergmbh.de>
To:	Sam Ravnborg <sam@...nborg.org>
cc:	LKML <linux-kernel@...r.kernel.org>,
	linux-kbuild <linux-kbuild@...r.kernel.org>
Subject: Re: [RFC] __ref annotation of function/data referencing __init/__exit


On Jan 28 2008 22:38, Sam Ravnborg wrote:
>On Sat, Jan 26, 2008 at 07:44:54PM +0100, Sam Ravnborg wrote:
>> Today we have the following annotations for functions/data
>> referencing __init/__exit functions / data:
>> 
>> __init_refok for functions
>> __initdata_refok for data
>> 
>> and
>> _exit_refok for functions
>> 
>> To simplify it and to introduce a shorter annotation I
>> will suggest the following annotation:
>> 
>> __ref      <= for functions (code) that
>>               references __*init / __*exit
>> __refdata  <= for variables
>> __refconst <= for const variables
>>
>
>This patch was includedin todays kbuild.git submission
>as I heard no negative feedback.

I would like to see some real-world example of __ref*.
When would you want to "reference" (function pointer?) an __init
function from outside another __init function?
--
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/