From: Michal Hocko <mhocko@kernel.org>
To: zhongjiang <zhongjiang@huawei.com>
Cc: akpm@linux-foundation.org, jhubbard@nvidia.com,
linux-mm@kvack.org, minchan@kernel.org
Subject: Re: [PATCH v2] mm: do not export ioremap_page_range symbol for external module
Date: Tue, 24 Jan 2017 11:23:19 +0100 [thread overview]
Message-ID: <20170124102319.GD6867@dhcp22.suse.cz> (raw)
In-Reply-To: <1485173220-29010-1-git-send-email-zhongjiang@huawei.com>
On Mon 23-01-17 20:07:00, zhongjiang wrote:
> From: zhong jiang <zhongjiang@huawei.com>
>
> 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.
>
> Signed-off-by: zhong jiang <zhongjiang@huawei.com>
> Reviewed-by: John Hubbard <jhubbard@nvidia.com>
> Suggested-by: John Hubbard <jhubbard@nvidia.com>
git grep says that there are few direct users of this API in the tree.
Have you checked all of them? The export has been added by 81e88fdc432a
("ACPI, APEI, Generic Hardware Error Source POLL/IRQ/NMI notification
type support").
Other than that this looks reasonably to me.
> ---
> lib/ioremap.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/lib/ioremap.c b/lib/ioremap.c
> index 86c8911..a3e14ce 100644
> --- a/lib/ioremap.c
> +++ b/lib/ioremap.c
> @@ -144,4 +144,3 @@ int ioremap_page_range(unsigned long addr,
>
> return err;
> }
> -EXPORT_SYMBOL_GPL(ioremap_page_range);
> --
> 1.8.3.1
--
Michal Hocko
SUSE Labs
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-01-24 10:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-23 12:07 zhongjiang
2017-01-24 10:23 ` Michal Hocko [this message]
2017-01-24 13:00 ` zhong jiang
2017-01-24 13:15 ` Michal Hocko
2017-01-24 13:26 ` zhong jiang
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=20170124102319.GD6867@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=jhubbard@nvidia.com \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=zhongjiang@huawei.com \
/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