The patch titled Subject: mm: do not export ioremap_page_range symbol for external module has been removed from the -mm tree. Its filename was mm-do-not-export-ioremap_page_range-symbol-for-external-module.patch This patch was dropped because it was merged into mainline or a subsystem tree ------------------------------------------------------ From: zhong jiang <zhongjiang@xxxxxxxxxx> Subject: mm: do not export ioremap_page_range symbol for external module Recently, I've found cases in which ioremap_page_range was used incorrectly, in external modules, leading to crashes. This can be partly attributed to the fact that ioremap_page_range is lower-level, with fewer protections, as compared to the other functions that an external module would typically call. Those include: ioremap_cache ioremap_nocache ioremap_prot ioremap_uc ioremap_wc ioremap_wt ...each of which wraps __ioremap_caller, which in turn provides a safer way to achieve the mapping. Therefore, stop EXPORT-ing ioremap_page_range. Link: http://lkml.kernel.org/r/1485173220-29010-1-git-send-email-zhongjiang@xxxxxxxxxx Signed-off-by: zhong jiang <zhongjiang@xxxxxxxxxx> Reviewed-by: John Hubbard <jhubbard@xxxxxxxxxx> Suggested-by: John Hubbard <jhubbard@xxxxxxxxxx> Acked-by: Michal Hocko <mhocko@xxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- lib/ioremap.c | 1 - 1 file changed, 1 deletion(-) diff -puN lib/ioremap.c~mm-do-not-export-ioremap_page_range-symbol-for-external-module lib/ioremap.c --- a/lib/ioremap.c~mm-do-not-export-ioremap_page_range-symbol-for-external-module +++ a/lib/ioremap.c @@ -144,4 +144,3 @@ int ioremap_page_range(unsigned long add return err; } -EXPORT_SYMBOL_GPL(ioremap_page_range); _ Patches currently in -mm which might be from zhongjiang@xxxxxxxxxx are z3fold-limit-first_num-to-the-actual-range-of-possible-buddy-indexes.patch mm-page_owner-align-with-pageblock_nr-pages.patch mm-walk-the-zone-in-pageblock_nr_pages-steps.patch -- To unsubscribe from this list: send the line "unsubscribe mm-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html