From: John Hubbard <jhubbard@nvidia.com>
To: zhongjiang <zhongjiang@huawei.com>,
akpm@linux-foundation.org, minchan@kernel.org, mhocko@kernel.org
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: do not export ioremap_page_range symbol for external module
Date: Sun, 22 Jan 2017 14:25:36 -0800 [thread overview]
Message-ID: <af4a9fec-03c8-d977-6fa6-a36f222e21ef@nvidia.com> (raw)
In-Reply-To: <1485089881-61531-1-git-send-email-zhongjiang@huawei.com>
On 01/22/2017 04:58 AM, zhongjiang wrote:
> From: zhong jiang <zhongjiang@huawei.com>
>
> Recently, I find the ioremap_page_range had been abusing. The improper
> address mapping is a issue. it will result in the crash. so, remove
> the symbol. It can be replaced by the ioremap_cache or others symbol.
Hi Zhong,
After thinking about this for a bit, and looking through our own (out-of-tree) kernel modules, I
think you have a good point. I just can't see any reason for a driver to call ioremap_page_range
directly. So the code change looks good to me.
For the commit description, here is a proposed re-wording, optional, that perhaps may be a little
clearer. See if you like it?
-------
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.
-------
I may get some heat for this if another out-of-tree driver needs that symbol, but if no one else
pops up and shrieks, you can add:
Reviewed-by: John Hubbard <jhubbard@nvidia.com>
thanks,
john h
>
> Signed-off-by: zhong jiang <zhongjiang@huawei.com>
> ---
> 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
>
--
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-22 22:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-22 12:58 zhongjiang
2017-01-22 22:25 ` John Hubbard [this message]
2017-01-23 1:14 ` zhong jiang
2017-01-23 1:30 ` John Hubbard
2017-01-23 11:52 ` 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=af4a9fec-03c8-d977-6fa6-a36f222e21ef@nvidia.com \
--to=jhubbard@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.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