linux-kernel - irqdesc: Why the "__ref" is needed in __irq_alloc

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:   Fri, 9 Mar 2018 15:07:47 +0800
From:   Dou Liyang <douly.fnst@...fujitsu.com>
To:     Thomas Gleixner <tglx@...utronix.de>,
        Kees Cook <keescook@...omium.org>, <re.emese@...il.com>,
        Marc Zyngier <marc.zyngier@....com>
CC:     <linux-kernel@...r.kernel.org>
Subject: irqdesc: Why the "__ref" is needed in __irq_alloc_descs() ?

Hi Maintainers,

I have a question about "__ref" in Linux kernel.

When I looked into the __irq_alloc_descs(), I found it tagged a
"__ref" mark, but I didn't find that it referenced code or data
from init section.

So, I confuse why the "__ref"  is needed in __irq_alloc_descs()?
any other reasons?

And after I tested, seems "__ref" just puts the code into a different
section that is not checked by modpost. It does not affect the
performance whether it is tagged or not. Is it right?

Thanks,
	dou.