From: Andrew Morton <akpm@linux-foundation.org>
To: Mark Vitale <mvitale@sinenomine.net>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
Dan Williams <dan.j.williams@intel.org>,
Joe Gorse <jgorse@sinenomine.net>,
"release-team@openafs.org" <release-team@openafs.org>,
Jerome Glisse <jglisse@redhat.com>
Subject: Re: [PATCH v4 0/8] mm: Rework hmm to use devm_memremap_pages and other fixes
Date: Fri, 20 Jul 2018 12:51:46 -0700 [thread overview]
Message-ID: <20180720125146.02db0f40b4edc716c6f080d2@linux-foundation.org> (raw)
In-Reply-To: <37267986-A987-4AD7-96CE-C1D2F116A4AC@sinenomine.net>
On Fri, 20 Jul 2018 14:43:14 +0000 Mark Vitale <mvitale@sinenomine.net> wrote:
> On Jul 11, 2018, Dan Williams wrote:
> > Changes since v3 [1]:
> > * Collect Logan's reviewed-by on patch 3
> > * Collect John's and Joe's tested-by on patch 8
> > * Update the changelog for patch 1 and 7 to better explain the
> > EXPORT_SYMBOL_GPL rationale.
> > * Update the changelog for patch 2 to clarify that it is a cleanup to
> > make the following patch-3 fix easier
> >
> > [1]: https://lkml.org/lkml/2018/6/19/108
> >
> > ---
> >
> > Hi Andrew,
> >
> > As requested, here is a resend of the devm_memremap_pages() fixups.
> > Please consider for 4.18.
>
> What is the status of this patchset? OpenAFS is unable to build on
> Linux 4.18 without the last patch in this set:
>
> 8/8 mm: Fix exports that inadvertently make put_page() EXPORT_SYMBOL_GPL
>
> Will this be merged soon to linux-next, and ultimately to a Linux 4.18 rc?
>
Problem is, that patch is eighth in a series which we're waiting for
Jerome to review and the changelog starts with "Now that all producers
of dev_pagemap instances in the kernel are properly converted to
EXPORT_SYMBOL_GPL...".
Is it in fact a standalone patch? Not sure. I'll see what the build
system has to say about that.
And it will need a new changelog. Such as
From: Dan Williams <dan.j.williams@intel.com>
Subject: mm: fix exports that inadvertently make put_page() EXPORT_SYMBOL_GPL
e76384884344 ("mm: introduce MEMORY_DEVICE_FS_DAX and
CONFIG_DEV_PAGEMAP_OPS") added two EXPORT_SYMBOL_GPL() symbols, but these
symbols are required by the inlined put_page(), thus accidentally making
put_page() a GPL export only. This breaks OpenAFS (at least).
Mark them EXPORT_SYMBOL() instead.
Link: http://lkml.kernel.org/r/153128611970.2928.11310692420711601254.stgit@dwillia2-desk3.amr.corp.intel.com
Fixes: e76384884344 ("mm: introduce MEMORY_DEVICE_FS_DAX and CONFIG_DEV_PAGEMAP_OPS")
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
Reported-by: Joe Gorse <jhgorse@gmail.com>
Reported-by: John Hubbard <jhubbard@nvidia.com>
Tested-by: Joe Gorse <jhgorse@gmail.com>
Tested-by: John Hubbard <jhubbard@nvidia.com>
Cc: Jérôme Glisse <jglisse@redhat.com>
Cc: Mark Vitale <mvitale@sinenomine.net>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
kernel/memremap.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff -puN kernel/memremap.c~mm-fix-exports-that-inadvertently-make-put_page-export_symbol_gpl kernel/memremap.c
--- a/kernel/memremap.c~mm-fix-exports-that-inadvertently-make-put_page-export_symbol_gpl
+++ a/kernel/memremap.c
@@ -321,7 +321,7 @@ EXPORT_SYMBOL_GPL(get_dev_pagemap);
#ifdef CONFIG_DEV_PAGEMAP_OPS
DEFINE_STATIC_KEY_FALSE(devmap_managed_key);
-EXPORT_SYMBOL_GPL(devmap_managed_key);
+EXPORT_SYMBOL(devmap_managed_key);
static atomic_t devmap_enable;
/*
@@ -362,5 +362,5 @@ void __put_devmap_managed_page(struct pa
} else if (!count)
__put_page(page);
}
-EXPORT_SYMBOL_GPL(__put_devmap_managed_page);
+EXPORT_SYMBOL(__put_devmap_managed_page);
#endif /* CONFIG_DEV_PAGEMAP_OPS */
_
next prev parent reply other threads:[~2018-07-20 19:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-20 14:43 Mark Vitale
2018-07-20 19:51 ` Andrew Morton [this message]
2018-07-20 19:57 ` Jerome Glisse
2018-07-20 20:01 ` Matthew Wilcox
2018-07-20 20:17 ` Jerome Glisse
2018-07-21 16:11 ` Dan Williams
-- strict thread matches above, loose matches on Subject: below --
2018-07-11 5:14 Dan Williams
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=20180720125146.02db0f40b4edc716c6f080d2@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.org \
--cc=jglisse@redhat.com \
--cc=jgorse@sinenomine.net \
--cc=linux-mm@kvack.org \
--cc=mvitale@sinenomine.net \
--cc=release-team@openafs.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