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>
Cc: Joe Gorse <jhgorse@gmail.com>,
	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 22:40:01 -0700	[thread overview]
Message-ID: <a6a16c1c-3e80-2cf8-6d8d-1d0fc91008af@nvidia.com> (raw)
In-Reply-To: <CAPcyv4j=LFY31zn7yFXUrsrvzQEz=a92VLOa=Tp46JbGHhC7Xw@mail.gmail.com>

On 06/15/2018 10:22 PM, Dan Williams wrote:
> On Fri, Jun 15, 2018 at 9:43 PM, John Hubbard <jhubbard@nvidia.com> wrote:
>> 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:
[snip]
>>>>
>>>> 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.
> 
> Right, certainly flipping the key is a kernel internal detail since it
> is giving the dev_pagemap owner purview over all kernel page events,
> but put_page() users are silent consumers. And you're right there's
> currently no good way I see to export the 'producer' and 'consumer'
> side of the key with different export types.
> 

It's hard to imagine how anyone could end up using devmap_managed_key
in an out-of-tree driver, given that other related symbols are already
locked down with EXPORT_SYMBOL_GPL. So one easy fix might be to just
make it EXPORT_SYMBOL, with a comment that explains the intent, and just
call it a day:

/* This is intended to be EXPORT_SYMBOL_GPL, but actually doing so would
 * cause a problem for put_page().
 */
EXPORT_SYMBOL(devmap_managed_key);

...I'm sort of winging it here... :)

      reply	other threads:[~2018-06-16  5:40 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
2018-06-16  5:22     ` Dan Williams
2018-06-16  5:40       ` John Hubbard [this message]

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=a6a16c1c-3e80-2cf8-6d8d-1d0fc91008af@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