linux-kernel - Re: Reqeust export symbol for API in arch/arm64/*

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: <20200506125315.GH8043@willie-the-truck>
Date:   Wed, 6 May 2020 13:53:16 +0100
From:   Will Deacon <will@...nel.org>
To:     �ֵ���/DONGHYEOK CHOE 
        <d7271.choe@...sung.com>
Cc:     linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
        hosung0.kim@...sung.com, changki.kim@...sung.com,
        hajun.sung@...sung.com, gregkh@...gle.com, youngmin.nam@...sung.com
Subject: Re: Reqeust export symbol for API in arch/arm64/*

On Wed, May 06, 2020 at 09:46:45PM +0900, �ֵ���/DONGHYEOK CHOE wrote:
> I am software engineer in charge of BSP (Samsung SOC vendor).
> 
> Recently, Google introduced GKI from Android R version.
> We cannot use mainline API without 'export symbol' by the GKI policy.
> But we want to make an arm64 specific vendor driver in {kernel source
> root}/drivers/soc/samsung/*.
> 
> Could you support us to use the below APIs?

Sorry, but as a general rule of thumb the kernel doesn't EXPORT symbols
that are not used by in-tree modules. You'll need to submit your drivers
along with the patches doing the exports if they are to be considered
for inclusion.

Thanks,

Will