From: hareeshg@codeaurora.org (Hareesh Gundu)
To: linux-security-module@vger.kernel.org
Subject: [PATCH] security: Export few symbols referred by other modules
Date: Wed, 6 Dec 2017 20:45:01 +0530 [thread overview]
Message-ID: <0322ddc2-f1a2-93f5-d34d-d57f6be734a3@codeaurora.org> (raw)
In-Reply-To: <201712052221.HDJ00044.tOOHVMFQFOJLSF@I-love.SAKURA.ne.jp>
On 12/5/2017 6:51 PM, Tetsuo Handa wrote:
> James Morris wrote:
>> On Tue, 5 Dec 2017, Hareesh Gundu wrote:
>>
>>> Export mmap_min_addr and security_mmap_addr() to allow
>>> kernel modules to use them.
>>>
>>> Signed-off-by: Hareesh Gundu <hareeshg@codeaurora.org>
Can other folks comment whether this should be EXPORT_SYMBOL or
EXPORT_SYMBOL_GPL ?
>> I'm not sure whether this should be EXPORT_SYMBOL or EXPORT_SYMBOL_GPL, as
>> this hook was added in 2009, well after EXPORT_SYMBOL_GPL came into being.
>>
>> Most of the LSM hooks are marked EXPORT_SYMBOL because they were part of
>> an existing interface when EXPORT_SYMBOL_GPL was introduced, IIRC.
>>
>> What do folks think?
>>
?That's right, This change is for outside kernel tree modules.
> We don't export symbols not used by in-tree modules.
> Which in-tree module needs to access these symbols?
>
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-12-06 15:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-05 10:58 [PATCH] security: Export few symbols referred by other modules Hareesh Gundu
2017-12-05 12:04 ` James Morris
2017-12-05 13:21 ` Tetsuo Handa
2017-12-06 15:15 ` Hareesh Gundu [this message]
2017-12-06 15:32 ` Greg KH
2017-12-07 0:10 ` James Morris
2017-12-05 13:34 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0322ddc2-f1a2-93f5-d34d-d57f6be734a3@codeaurora.org \
--to=hareeshg@codeaurora.org \
--cc=linux-security-module@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).