linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: John Hubbard <jhubbard@nvidia.com>
To: Dan Williams <dan.j.williams@intel.com>, Joe Gorse <jhgorse@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux MM <linux-mm@kvack.org>, Christoph Hellwig <hch@lst.de>
Subject: Re: OpenAFS module libafs.ko uses GPL-only symbol '__put_devmap_managed_page'
Date: Fri, 15 Jun 2018 21:43:33 -0700	[thread overview]
Message-ID: <1970355c-ebca-7f7d-38f7-ceac1ae553fb@nvidia.com> (raw)
In-Reply-To: <CAPcyv4hpjNaUz6qpJ0_Wh1SAz9tS9a5HLsYSgeCh_pNZKfY74A@mail.gmail.com>

On 06/13/2018 12:51 PM, Dan Williams wrote:
> [ adding Andrew, Christoph, and linux-mm ]
> 
> On Wed, Jun 13, 2018 at 12:33 PM, Joe Gorse <jhgorse@gmail.com> wrote:
>> Greetings,
>>
>> Please CC answers & comments to this email. Thanks! =)
>>
>> Our build is breaking as of
>> commit e7638488434415aa478e78435cac8f0365737638
>> Author: Dan Williams <dan.j.williams@intel.com>
>> Date: Wed May 16 11:46:08 2018 -0700
>>
>> mm: introduce MEMORY_DEVICE_FS_DAX and CONFIG_DEV_PAGEMAP_OPS
>> ... snip ...
>> https://patchwork.kernel.org/patch/10412459/
>>
>> We do not directly use the GPL-only symbol '__put_devmap_managed_page'. It
>> appears to be picked up from static-inlining in put_page(), which we need.
>>
>> How shall we proceed? Would it be reasonable to request the change of the
>> GPL-only exports for this commit?
>>
>> Cheers,
>> Joe Gorse
>>
>> P.S. The build failure, for the morbidly curious:
>>> FATAL: modpost: GPL-incompatible module libafs.ko uses GPL-only symbol
>>> '__put_devmap_managed_page'
>>> scripts/Makefile.modpost:92: recipe for target '__modpost' failed
>>> make[6]: *** [__modpost] Error 1
> 
> I think the right answer here is to make __put_devmap_managed_page()
> EXPORT_SYMBOL(), since features like devm_memremap_pages() want to
> change the behavior of all users of put_page(). It again holds that
> devm_memremap_pages() needs to become EXPORT_SYMBOL_GPL() because it,
> not put_page(), is the interface that is leaking control of core
> kernel state/infrastructure to its users.
> 

Hi Dan and all,

It looks like put_page() also picks up one more GPL symbol: 
devmap_managed_key.

put_page
    put_devmap_managed_page
        devmap_managed_key

    __put_devmap_managed_page


So if the goal is to restore put_page() to be effectively EXPORT_SYMBOL
again, then I think there would also need to be either a non-inlined 
wrapper for devmap_managed_key (awkward for a static key), or else make
it EXPORT_SYMBOL, or maybe something else that's less obvious to me at the
moment.


thanks,
-- 
John Hubbard
NVIDIA

  reply	other threads:[~2018-06-16  4:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAFhSwD9RNcsaTNdT-4DiE_BKK6zrsdBbNbGBEkBoJuwQn1JdQA@mail.gmail.com>
2018-06-13 19:51 ` Dan Williams
2018-06-16  4:43   ` John Hubbard [this message]
2018-06-16  5:22     ` Dan Williams
2018-06-16  5:40       ` John Hubbard

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=1970355c-ebca-7f7d-38f7-ceac1ae553fb@nvidia.com \
    --to=jhubbard@nvidia.com \
    --cc=akpm@linux-foundation.org \
    --cc=dan.j.williams@intel.com \
    --cc=hch@lst.de \
    --cc=jhgorse@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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