All of lore.kernel.org
 help / color / mirror / Atom feed
From: zhong jiang <zhongjiang@huawei.com>
To: Michal Hocko <mhocko@kernel.org>
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 21:26:30 +0800	[thread overview]
Message-ID: <58875606.7090504@huawei.com> (raw)
In-Reply-To: <20170124131548.GJ6867@dhcp22.suse.cz>

On 2017/1/24 21:15, Michal Hocko wrote:
> On Tue 24-01-17 21:00:24, zhong jiang wrote:
>> On 2017/1/24 18:23, Michal Hocko wrote:
>>> 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").
>>   I have checked more than one times.  and John also have looked through the whole own kernel.
> OK, it seems you are right. Both PCI_TEGRA and ACPI_APEI_GHES are either
> disabled or compiled in. The same applies for drivers/pci/pci.c.
> This wasn't the case at the time when the export was introduced as
> ACPI_APEI_GHES used to be tristate until 86cd47334b00 ("ACPI, APEI,
> GHES, Prevent GHES to be built as module").
>
> You can add
> Acked-by: Michal Hocko <mhocko@suse.com>
 Thanks a lot.

--
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>

      reply	other threads:[~2017-01-24 13:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-23 12:07 [PATCH v2] mm: do not export ioremap_page_range symbol for external module zhongjiang
2017-01-24 10:23 ` Michal Hocko
2017-01-24 13:00   ` zhong jiang
2017-01-24 13:15     ` Michal Hocko
2017-01-24 13:26       ` zhong jiang [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=58875606.7090504@huawei.com \
    --to=zhongjiang@huawei.com \
    --cc=akpm@linux-foundation.org \
    --cc=jhubbard@nvidia.com \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@kernel.org \
    --cc=minchan@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.